Topic: IDEA: drag window to edge automatically resizes it (Read 1,304,158 times)
Hey ppass.
About the suggestions regarding fastmove:
Currently, none of those are possible, simply because 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. It's not impossible to implement your suggestions, only something i can't do right now.
About having the windows move to the other screen... You can make your own gird, which could have for example in monitor 1, an element that would move the window to monitor 2, and in mornitor 2 would have an element that would move to monitor 1.
ps: I have attached to this post, another version of axcrusik's grid, which allows you to, in conjuntion with being able to move windows with the numpad, move them in a way that makes more sense.
To install it, just add it to the "grids" folder of gridmove, and replace the earlier version.
Another interesting feature is that now you can add a modifier to reach for numbers higher than 10 faster. Check on the ini file, and set the key FastMoveMeta like this:CodeThat will allow you to move a window to area 11 by pressing win+\ followed by 1 (instead of 11 like when you press win+g).FastMoveMeta=\
; given W as window, D as direction pushed (1-8)
nearestDistance := MAX_INT ; or some arbitrary large number
nearestGroup := 0
maximumDistance := 50 ; this would be set through the UI
minimumDistance := 4 ; for rounding errors, perhaps?
for each G in Groups
distance := abs(G.left - W.left) + abs(G.right - W.right) + abs(G.top - W.top) + abs(G.bottom - W.bottom)
if distance < nearestDistance
nearestDistance := distance
nearestGroup := G
if nearestDistance < minimumDistance
; this is most likely it; quit looking.
break
end if
end if
end for
if nearestDistance < maximumDistance
; this window is 'close enough' to nearestGrid; move from there
Move(W, NextGrid(nearestGrid, D))
else
; this window is too far from nearestGrid; move to there
Move(W, nearestGrid)
end if[1]
TriggerTop = [Monitor1Top] + [Monitor1Height] /3 *2
TriggerRight = [Monitor1Left] + [Monitor1Width] /3
TriggerBottom = [Monitor1Bottom]
TriggerLeft = [Monitor1Left]
GridTop = [Monitor1Top] + [Monitor1Height] /3 *2
GridRight = [Monitor1Left] + [Monitor1Width] /3
GridBottom = [Monitor1Bottom]
GridLeft = [Monitor1Left]
GridNext = 2,5,4,1,1,1,1,1
if(WinWidth > 3 * TitleSize)
{
If (TitleSize < WinWidth - 100 AND LButtonDrag
AND OldmouseX > TitleLeft AND OldMouseX < TitleSize
AND MouseControl = "")
{
Hotkey = LButton
sendinput {LButton up}
GoSub,DropZoneMode
Settimer, MousePosition,10
return
}
}
else
{
If (LButtonDrag AND OldmouseX > TitleLeft
AND OldMouseX < TitleLeft + 20 AND WinWidth > 170
AND MouseControl = "")
{
Hotkey = LButton
sendinput {LButton up}
GoSub,DropZoneMode
Settimer, MousePosition,10
return
}
}
).Hi mojo-chan!
I really don't know why that happens, never happened to me.
I just tried it, but couldn't reproduce (probably because i only have keepass 1.11
Have you seen this happen with any other program?
I found a bug
When you make a window "on top", it does stay on top at first. However, when certain things happen to it, it looses the "on top" attribute.
kwacky1: I think that constantly setting windows to be ontop would potentially take too much processor time, and only help a few programs.
mojo-chan: I did try to add stuff to the window menu (or the window title, next to the other 3 buttons), but have found there's no reliable way to do it with Autohotkey, the language GridMove is built with.
Original address: https://www.donationcoder.com/forum/index.php?topic=3824.0