Messages

1

JGPaiva's GridMove and Ahk Tools / Re: GridMove: Grids Here

« on: February 05, 2013, 12:49 AM »

Same as above, but adds roughly a 66%/33% horizontal split to any 2nd monitor in pivot mode.

2

JGPaiva's GridMove and Ahk Tools / Re: GridMove: Grids Here

« on: February 04, 2013, 11:01 PM »

Keeping it simple: Dual & Quad splits.
Additionally, the top left quarter has an optional split down its middle, for when you want two small (notepad) windows in there.

In the first pic below, the divisions represented by broken (dotted) lines are optional.
The second pic shows you the layout of the triggers.
The triggers are not as big as their corresponding areas, which makes it easy to "undo" the move by letting go of the mouse button outside of a trigger, and gives you more options.

3

JGPaiva's GridMove and Ahk Tools / Re: GridMove: Grids Here

« on: September 28, 2008, 04:43 AM »

Crap. I had a look too (ok, briefly) and overlooked that "t".

4

JGPaiva's GridMove and Ahk Tools / Re: GridMove: Grids Here

« on: September 01, 2008, 10:46 AM »

Thanks for your kind response and your great program.

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.

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.

5

JGPaiva's GridMove and Ahk Tools / Re: GridMove: Grids Here

« on: September 01, 2008, 02:33 AM »

Grid for 30" monitors
I 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.)

Grid File: Roenie - 2x2 with Sidebar Reverse.grid

Hot spots
Instead 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.

Columns
The 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.

Versatility
I 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 closing
Let me know if you like this grid.

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.)

Edit: fixed grid download link