Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.

You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.

Hi All I have a dual monitor set up on a Matrox dual head to go. I'm trying to put together a grid so t5hat monitor 1 shows a full window and monitor 2 has a 2/3 width full height window and two half height windows on the remaining third(remembering of course that a dual head to go sees both monitors as just one single large monitor.) Heres what I put together using the tutorial but as you can guess it does not work!! I do understand that this is using very simple grids and triggers but it is only a starting point!

Hi kranor!I'm really not that surprised that you can't make that grid, it isn't that easy and my poor english doesn't help Ok, from what i understand, the first one is correct, right?I think the grid i posted below should do it. I also attached it to the post so it's easier to import.I really appreciate it that you tried it yourself, looks like you made a real effort Sorry for making this such a complex problem, but i really couldn't figure out a better way to make grids. (specially since the gridmaking utility really sucked )

I thought I would post this grid. Its a variation of the 3 part dual screen grid, this has the edges for vertical maximize in the 1/3 area--but the two 2/3 areas are in the middle. Also note that AFTER I created this grid, I realized my monitor arrangement was 2,1.........NOT 1,2.

This arrangement is in 2-mon-ports-better-triggers.grid, but this one is just 2/3-1/3 split without all the trigger areas.This grid was created for 2 24 inch widescreen monitors.

WOW!! This is the BEST tool I've EVER discovered!! As a web developer I am ALWAYS working with at least two windows open - and up to EIGHT! And I've always thought how wonderful it would be to be able to just get the windows into a grid to do my work ... and this tool and all of your great custom grids are just awesome!

Now I'm trying all of the grids to see which work best for me in which stages of development that I am in at the time ... and considering making some of my own as soon as I complete my current project.

And I thought Mobysaurus was great ... little did I know there was even better stuff here!! ;-) I'm SO glad that DonationCoder has us come back to get a new key - if not I may not have ever discovered this life saver!

HUGE KUDOS to DonationCoder and all of you for this SUPER tool!! As soon as I get paid for this project I'm making a donation for sure!

For anyone who's wondering what GridStack is, here's the explanation:GridStack is a great app that Xitsa created, to make your own grids for GridMove, using simpler ways to define them.You can download and read more about it here.

Xitsa: I think the grids on the previous posts are a bit different from yours, since they use 2/3 of the screen on grid element '1'.

Xitsa: I think the grids on the previous posts are a bit different from yours, since they use 2/3 of the screen on grid element '1'.

Maybe, my main aim was to show ease of changing layouts and give some examples.GridStack is useful for quick creating of simple layouts, I know about it's limitations and some of them where introduced specially to simplify input language.For example, yoda_97's grid cannot be get quick, it needs at least four steps:

Creating stack for triggers

Creating stack for three part–like layout

Creating stack for two part–like layout

Combining triggers windows with corresponding layouts

But at least with gridstack one can quickly get screen coordinates In principle, I can develop a more complex language that could describe grids where triggers layout different from window layout, but perhaps writing in it will be more cumbersome than using aforesaid procedure.

Grid for 30" monitorsI use a 30" monitor (2560x1600) and I've created an "advanced" grid for my personal use and anyone else who likes it. (If you do a lot of web browsing, you probably will.) It's made for 30" monitors and I have not tested it on smaller ones or lower resolutions. You could probably make that work if you wanted to because most are variables, not static values, but there isn't much of a point in doing so. (Some areas would become too small for practical use.)

Hot spotsInstead of making the trigger areas the same as the grid areas, I used large trigger hot spots. (A bit like EdgeGrid, but that was impractical for me.) Because of the trigger hot spots, you can:

-Exit drop-zone mode without moving the window, just by releasing the mouse button anywhere outside of the hot spots.-Move your mouse around inbetween the hotspots in drop-zone mode, without triggering the transparent overlay.-Have a grid layout that gives you a better idea of where the window positions really are.-Use smaller areas seperately or together as one larger area.

ColumnsThe grid has 3 columns. Two wide, one narrow. From right to left, they are vertically subdivided as follows (on a 2560x1600 monitor):

Column 1 - right) Two windows, browser-sized at 1024x800 because many websites are created with 1024x768 monitors in mind (or smaller). This happens to be a pretty decent size for other window types too.

Column 2 - middle) Same as 1, making it 4 main windows (2 by 2). The larger the area the larger the hotspot, so these 4 main areas are easy to identify.

Column 3 - left) Narrower than the other two, this is the remaining horizontal space (512 W x 1600 H) and is vertically divided into two areas of size 512 x 800. The bottom one of these is then divided into two narrow list-shaped areas for winamp and/or instant messenger buddy lists.

VersatilityI tried to make it versatile. All three columns have a horizontal trigger bar at the top that maximizes the window to that column, vertically. Column 3 also has one of these horizontal trigger bars in the middle, it allows you to use the two list-shaped areas as one wider area. In short, column 3 can be used as one area, two areas, or three, depending on the hotspots you use.

There's also a hot spot in either bottom corner of the screen. They can be used to "maximize" a window to make it span the left 2 columns or the right 2 columns (covering all 4 main screens). This can be used for e.g. a large photoshop window and then you still have the third column available for other (browser) windows.

In closingLet me know if you like this grid.

Sorry I don't yet have a regular version, only the Reverse version. I prefer reverse style and these grids take quite a bit of time and effort to create. You can always use the Reverse grid to make your own Regular grid if you want to. I might post a Regular version at a later time.

GridMove rules! (Wouldn't it be nice if we could just drag the gridlines around, instead of editing a .grid file? It would make the program a helluva lot more adaptable & versatile.)

Hi Roenie!!Welcome to DC, and what a great first post I really like the concept of your grid, and how it works for you, you've made a great job there

The bad news for the rest of the people is that it really only works on a huge screen like Roenie, I've tried it on my 20' (1680x1050), and it doesn't look as good as in yours since some of the areas are fixed-width and fixed-location, to look just right on a big screen.

(Wouldn't it be nice if we could just drag the gridlines around, instead of editing a .grid file? It would make the program a helluva lot more adaptable & versatile.)

Actually, I'm going through the process of creating a grid creator, but I think it wouldn't still be very useful in your case, because it won't allow you to create triggers with sizes different from the grid elements. (which is quite an advanced feature, congrats for figuring that out ).

The bad news for the rest of the people is that it really only works on a huge screen like Roenie, I've tried it on my 20' (1680x1050), and it doesn't look as good as in yours since some of the areas are fixed-width and fixed-location, to look just right on a big screen.

Because a 30" dwarfs anything smaller, 24" screens included, it wouldn't make sense to try my grid on that anyway. There would be too many areas. You would want fewer areas so that they're big enough. So I could have made my life easier and just used absolute values only. I realized this when I was almost done, at which point I stopped bothering to use variables only.

Quote

Actually, I'm going through the process of creating a grid creator, but I think it wouldn't still be very useful in your case, because it won't allow you to create triggers with sizes different from the grid elements.

Yea I was thinking the same thing... but it would make the initial creation of the basic grid much quicker. (I don't consider GridStack very easy as it took me a while to understand it, even though I understand java style syntax.) The worst part about creating a grid from scratch is to calculate the dividers you need for screen width and height , to set each area's borders.

Wouldn't it be a good idea to seperate the grid zones and the trigger zones in the .grid file, so that they really are two seperate sections in the file? Then use one line (e.g. "Tag=") to link a grid zone to its trigger zone. Then it would be easier to create trigger zones as well as grid zones using a tool. You can just link them later.

I just discovered this nifty little tool and immediately had to make my own grid. As it took me a couple of hours, I certainly want to share it with you now!

The grid is called 100possibilities, because it offers you exactly one hundert possibilities to position a window.

The screen basically is divided in 4x4 equally sized rectangles, where you can position the window anyway you like. The grid may look a bit complicated in the beginning (and you should really disable the numbers), but the usage is actually rather intuitive:

To occupy a single cell of the grid, just drag the window in the center of the cell.

To occupy two adjacent cells, drag the window in the middle between the cells.

To occupy three adjacent cells, drag the window in the space between the 'cell hotspot' and the 'two adjacent cells hotspot'.

If you drag the mouse horizontally, you only change the width of the window.

If you drag the mouse vertically, you only change the height of the window

To occupy any formation across the whole screen (e.g. one whole column, two whole columns=left/right half of the screen, two whole rows=lower/upper half of the screen, etc.) just drag along the border of the screen.

Ok, people please don't take this wrongly, but lujomu's grid is just... Perfect!It goes beyond grids, it's VERY flexible, and I agree with its 100 possiblities, if you have a screen large enough to use it, it allows you to place windows EXACTLY as you'd like, and it's impressive how easy it is to use!I was like "man, it's impressive how he predicted how I'm going to move the mouse to extend this area to the one on its left/right".

Thank you very much, lujomu. I'm glad you took the time to make this grid

If you don't mind, I'd like to include this grid as a default grid with GridMove in the next release I make!

I'm really glad you like it, as it was a lot of work to plan the mostly overlapping hotspot fields to not have multiple hotspots for a single window position. This reduced the hotspot count from 221 (if you made a single hotspot for every rectangle you see in the grid) to just 99 per screen. So you see, the 100 possibilities are not just an estimation, they are counted (99 different window positions + maximized window)!

Actually I created the grid for my 21" monitor in mind, but as I started testing it on my 13.3" notebook display, I was really amazed on how well it works even on that small screen! Admitted, a single cell window won't be too useable in the most cases (maybe big enough for a instant messanger window though?), but who says you have to use cell-sized windows? Even the smaller hotspots (for the more eccentric dimensions like 3x2 or 3x3) are still big enough to be selected easily!

If you don't mind, I'd like to include this grid as a default grid with GridMove in the next release I make!

Sure, go ahead. It would be an honor to me!

The only drawback I found with this grid so far is, that it sometimes needs a couple of seconds to show up. I assume this is due to almost 200 hotspots for two monitors. And this brings me to some suggestion for GridMove:

Would it be possible to use something like e.g. [MonitorTop] instead of [Monitor1Top] and [Monitor2Top], to specify the hotspots for all connected monitors? Thus reducing the number of hotspots to a half if you use the same grid on all monitors.

I would really like to be able to define my own variables in the grid-files. This could make the grid-files easier to adapt and easier to read and understand. Explanation:

If any of my suggestions are already possible, I apologize in advance for my ignorance. As I said, I just discovered GridMove yesterday and may certainly have missed something.

And you made this complex grid? Incredible!

About your suggestions..Adding [MonitorTop] wouldn't really help much, speed-wise. The problem is that drawing the grid for that many "hotspots" (yeah, that sounds WAY better than grid elements ) takes some time. Usually, for smaller grids, this isn't noticeable.About defining your own variables... I think someone also suggested that, and I think it makes sense. I'm not sure if I could do it, but I'll add it to my todo list

First grid here. I tried GridMove and my first thought was: "It doesn't work, WTF!". It seems that Google Chrome handles windows by itself, mimicking vista look and feel using some weird libraries on XP. (note to Joao: It doesn't move them at all, possible bug or exception?)

Anyway as soon as I tried it with my usual soft I felt in love, and of course had to tweak grids. I liked dualscreen, so took a look at grid file... Oh god, no grid file. No gvim to the rescue, let's read some code. No luck.

Anyway, I don't discover such gems everyday so had to try it. My setup is two Dell 20" widescreens, one horizontal in front, one vertical on right hand side. Excogitation grid seemed so cool but needed to change it so I get split 1/2 on vertical monitor and a couple of maximize edges for my lovely 1050x1680 Word. I tried hard but I'm unable to fix a weird issue.

In my grid file I defined 26 groups. Gridmove parses it ok, but only displays 24. I have no clue about what's going on. Group 15 and 16 are not displayed, and triggers move to next defined group. I labeled them pesty top left 1/2, pesky bottom left 1/2. Grid is usable right now, and those groups wouldn't not be used so often by me so I decided to contribute with my file. Can anyone detect why does it jump some groups?

"I suppose it can be said that I'm an absent-minded driver. It's true that I've driven through a number of red lights on occasion, but on the other hand, I've stopped at a lot of green ones but never gotten credit for it."Glenn Gould

Satch: the problem with your grid's 15th and 16th hotspots is simple: it's the variables. In TriggerRight, there's a variable named "monitor2witdth". This causes GridMove to ignore the hotspots. Yeah, there should be some time of warning, but this is used to prevent the hotspots from being drawn when there isn't a second (or third, etc) monitor.

About Chrome.. I haven't been able to fix that problem because apparently that problem has been fixing itself!I've tried to debug it, but both times I talked to the users having the problem, it just stopped happening without anyone doing anything!

Oh God, this is awesome. Here is my working satch.grid in case anyone is interested.

I've been using Gridmove using keybindings extensively. I've got a Logitech G11 with 18x3 extra keys. So I bound G6 to maximize window on right hand monitor. G9 to top right monitor, G12 to bottom right. G8 for maximize left, G10 left monitor half left and G11 left monitor half right. Every binding was created using Fast Switching mode using Ctrl+Win+GridNumber. As I couldn't get it working with two digits, moved my hotspots numbers to fit.