51
JGPaiva's GridMove and Ahk Tools / Re: (Feature Request) Arrow keys to move windows inside grid
« on: September 13, 2008, 03:46 AM »
Could you hint a date when you can implement the ideas discussed last January (step2 of Gridmove)?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
So many times, after using many different USB drives (HDs, USB sticks...), windows gets all mixed up and starts assigning unusual letters to my drive, which makes backuping, errrrrr, an interesting experience.-Armando (September 03, 2008, 12:05 AM)
Your idea on how to implement the horizontal/vertical cycle realy simplifies things, and maybe it really is the simplest way to implement it. I'll give it some thought.-jgpaiva (January 07, 2008, 05:37 AM)
Regarding step 2 of "cycle grid elements", i know exactly how to do it, but i'll have to wait for some time to implement it since it involves quite a few changes to the way gridmove works.-jgpaiva (January 07, 2008, 06:57 PM)
Actually, the problem is a little different. Some windows don't resize to larger sizes than the screen. (windows explorer is a good example.) Thus, When you try to resize them using that second grid element, they don't get the correct size, and don't get identified as being in grid 2 when you press win+left. If you try that with a window that does resize to a size larger than the screen (which is very rare, from what i can see), you'll notice that it does work as expected.-jgpaiva (January 08, 2008, 05:03 AM)
"no match for grid" pops up everytime the program tries to match that window agains the grid and can't find any match. I can't understand why you'd press right and then left, if it fails on right, it'll fail on left too as they both use the same mechanism..-jgpaiva (January 07, 2008, 05:37 AM)
Regarding step 2 of "cycle grid elements", i know exactly how to do it, but i'll have to wait for some time to implement it since it involves quite a few changes to the way gridmove works.-jgpaiva (January 07, 2008, 06:57 PM)
Ok,i added the "step 1" you mentioned (actually, it's pretty fun! Not sure if it's that useful, though).-jgpaiva (January 06, 2008, 05:21 PM)
Regarding the step2, it'd have to be made in the following way: each grid element would say what was the grid on its right, the grid on its left and the grid on its top and bottom. I think it'd be quite a chore to implement and then to create grids with these features, though.-jgpaiva (January 06, 2008, 05:21 PM)
The reason why i don't know how to add this to gridmove is because it's not easy to detect which grid element is on the right or left of the current one. When we have a 3-part grid, or a 4 part grid, it's easy, but when we have something like the edge grid or something, things become very confusing...
Maybe this could be added as a coding snack? I don't think it'd be that hard to reproduce freesnap with ahk...-jgpaiva (January 06, 2008, 05:30 AM)
Unfortunatelly, many windows don't actually get the size they are moved toWell, I have no clue how you are doing this, but I recently discovered Windows API functions. I played a bit with some of them in VBA, and this quite straight forward. I assume in your case you have to use the GetWindowRect Function
gridmove isn't aware of where the window is. I mean, it only moves the window to a grid, and doesn't keep track of which windows are in which grids.That is fortunate, and obviously the most efficient way to program this.-jgpaiva (December 12, 2007, 05:15 AM)
It's not impossible to implement your suggestions, only something i can't do right now.-jgpaiva (December 12, 2007, 05:15 AM)