AutoHotkey Homepage AutoHotkey Community
Let's help each other out
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

WindowPad - multi-monitor window-moving tool
Goto page Previous  1, 2, 3 ... 14, 15, 16, 17  Next
 
Post new topic   Reply to topic    AutoHotkey Community Forum Index -> Scripts & Functions
View previous topic :: View next topic  
Author Message
Lexikos



Joined: 17 Oct 2006
Posts: 4469
Location: Qld, Australia

PostPosted: Sun Aug 02, 2009 10:03 am    Post subject: Reply with quote

The closest equivalent without modifying WindowPad.ahk would be to add this to the [Hotkeys] section of WindowPad.ini:
Code:
!WheelUp = MaximizeToggle
However, there's nothing to stop you from simply adding the hotkey to WindowPad.ahk as you would with any other script.
Back to top
View user's profile Send private message Visit poster's website
Guest






PostPosted: Sun Aug 02, 2009 10:05 am    Post subject: Reply with quote

what?? i tried like endlessly, i must be doing something wrong... you saying i can just put
!Wheelup::WinMaximize, A
at the start of the .ahk or the end and it should work? cuz it def did not.
Back to top
Guest






PostPosted: Sun Aug 02, 2009 10:10 am    Post subject: Reply with quote

ok sorry i put it at the end of the AHK and now it works, ASFDLKHGL damn, i tried putting it everywhere else, and there too i thought, sigh
Back to top
vj
Guest





PostPosted: Wed Aug 19, 2009 9:45 pm    Post subject: Works great on Windows 7 RTM Reply with quote

I was just looking for moving windows between dual monitors. This tool works great without any issue in Windows 7 RTM.

Thanks.
Back to top
ReeseCup
Guest





PostPosted: Fri Sep 11, 2009 3:06 am    Post subject: Reply with quote

Is there anyway to call the various commands using a command line switch?

I'd like to be able to have a shortcut that would start WindowPad.exe, have it gather windows on monitor 2 and move them to monitor 1 and then shut itself down.

I have a KVM feeding my second monitor and occasionally need to be able to move all my windows from the second monitor to my primary monitor. This doesn't happen that often though and I don't want another program running in the background needlessly. If I could pass /GatherWindows, 1 via command line, that would be excellent.

I have to admit, I'm going to continue to use this awesome utility whether it handles command line switches or not. It too useful to deny. Cool
Back to top
Lexikos



Joined: 17 Oct 2006
Posts: 4469
Location: Qld, Australia

PostPosted: Fri Sep 11, 2009 3:18 pm    Post subject: Reply with quote

Quote:
Version 1.56:
  • Added command-line mode.
  • Tweaked tray menu.
  • Tweaked version info for WindowPad.exe.
  • Create WindowPad.ini automatically if it doesn't exist, rather than including WindowPad.ini in the distribution and risking overwrite of existing configuration. Default contents are defined by WindowPad.Default.ini or embedded in WindowPad.exe.
Quote:
As of v1.56, WindowPad supports a command-line mode. Simply pass one or more commands on the command-line and WindowPad will execute them and then exit. If a command's parameters contain spaces, the command and its arguments must be enclosed in quotation marks. For example:
Code:
WindowPad.exe GatherWindows,1 "WindowScreenMove, Next, My Window"

I prefer not to add #SingleInstance Off, so if WindowPad is already running and you want to run a command-line without replacing the existing instance, use the /F switch:
Code:
WindowPad.exe /F GatherWindows,1
Back to top
View user's profile Send private message Visit poster's website
ReeseCup
Guest





PostPosted: Fri Sep 11, 2009 8:35 pm    Post subject: Reply with quote

I've downloaded the update and it work's flawlessly.

Thank you so much for putting together a simple, useful utility, sharing it with the world and continuing to improve it.

You and your code are awesome. Very Happy
Back to top
Guest






PostPosted: Tue Sep 22, 2009 4:16 am    Post subject: Reply with quote

I think I discovered the following bug on Vista SP2 (32bit).

When I change the DPI size (to get bigger fonts) in Control Panel\Personalization, then there seems to be an issue with WindowPad.

It looks like that WindowPad can not handle to new DPI setting correctly. WindowPad makes all window smaller.

Did you also notice this?
Back to top
wrecklass



Joined: 19 Mar 2007
Posts: 28

PostPosted: Sun Sep 27, 2009 8:14 pm    Post subject: Reply with quote

Not sure if the WindowPad author is following this thread recently, but I was wondering if there is an option I can use in .ini to tell WindowPadMove to do just that. The current WindowPadMove moves and resizes the window. I just want a way to move the window on the current screen without always resizing it.

I can add my own function to do what I want, but before I go to the trouble of modifying the script I thought I'd ask.
Back to top
View user's profile Send private message
gh696



Joined: 27 Oct 2009
Posts: 2

PostPosted: Tue Oct 27, 2009 5:13 pm    Post subject: Reply with quote

Hi.

I really love this tool, makes my life much easier.

Everything is just perfect, accept for one little thing; I cant move all the minimized windows when i do the "move all-command", just the ones that are open moves to the other monitor.

I have copied the code on the first page of this thread.

Is there any newer versions than the first post, and does it fix the "minimized-problem" ?

Any response is much appreciated.

Edit: omg, i'm so dumb, i just saw the newest version on the first post, so don't mind that question... I still wonder how to move minimized windows though.
Back to top
View user's profile Send private message
Lexikos



Joined: 17 Oct 2006
Posts: 4469
Location: Qld, Australia

PostPosted: Tue Oct 27, 2009 10:29 pm    Post subject: Reply with quote

It's an intentional feature. I might add an option to move minimized windows, but I haven't had much time to code lately.
Back to top
View user's profile Send private message Visit poster's website
gh696



Joined: 27 Oct 2009
Posts: 2

PostPosted: Tue Oct 27, 2009 10:36 pm    Post subject: Reply with quote

Lexikos wrote:
It's an intentional feature. I might add an option to move minimized windows, but I haven't had much time to code lately.


It would be GREAT if you did though...

/KalleP
Back to top
View user's profile Send private message
Guest






PostPosted: Wed Nov 04, 2009 4:40 am    Post subject: Reply with quote

I am visually impaired and need to run windows 7 at 200% dpi. Unfortunately windowpad doesn't work, as the other user described already. Windowpad appears to divide the size of windows by two. If Width is one then the width actually becomes .5 and so on. Is this a bug?

Anonymous wrote:
I think I discovered the following bug on Vista SP2 (32bit).

When I change the DPI size (to get bigger fonts) in Control Panel\Personalization, then there seems to be an issue with WindowPad.

It looks like that WindowPad can not handle to new DPI setting correctly. WindowPad makes all window smaller.

Did you also notice this?
Back to top
Lexikos



Joined: 17 Oct 2006
Posts: 4469
Location: Qld, Australia

PostPosted: Thu Nov 05, 2009 10:44 am    Post subject: Reply with quote

Does this happen when you use a particular function/hotkey? Does it shrink further each time you repeat? If you simply double the width in the INI file, does that solve the problem?

I've just tested on a clean install of Vista (32-bit, no updates, Aero disabled) with 200% DPI, and it worked exactly the same as it does with 100% DPI. I could not see any problems.

I'll test again once Vista finishes updating. I may also test on Windows 7 the next time I reboot (which will be later, since Vista is running in VirtualBox on Windows 7...).
Edit: Also tested OK on Vista SP2.
Back to top
View user's profile Send private message Visit poster's website
Guest






PostPosted: Sun Nov 08, 2009 2:59 am    Post subject: Reply with quote

I assume you tested in virtual machine (because aero disabled)?

I tried with Vista and Windows 7 (nvidia graphics card). Same result on both OS.

Anyway, when I double the values (or to be more precise multiply the values with the exact DPI value), then Windowpad seems to work. May be I should modify the code, might be easier?

The resolution is 1920*1080.

Thanks for looking into this!



Lexikos wrote:
Does this happen when you use a particular function/hotkey? Does it shrink further each time you repeat? If you simply double the width in the INI file, does that solve the problem?

I've just tested on a clean install of Vista (32-bit, no updates, Aero disabled) with 200% DPI, and it worked exactly the same as it does with 100% DPI. I could not see any problems.

I'll test again once Vista finishes updating. I may also test on Windows 7 the next time I reboot (which will be later, since Vista is running in VirtualBox on Windows 7...).
Edit: Also tested OK on Vista SP2.
Back to top
Display posts from previous:   
Post new topic   Reply to topic    AutoHotkey Community Forum Index -> Scripts & Functions All times are GMT
Goto page Previous  1, 2, 3 ... 14, 15, 16, 17  Next
Page 15 of 17

 
Jump to:  
You can post new topics in this forum
You can reply to topics in this forum


Powered by phpBB © 2001, 2005 phpBB Group