AutoHotkey Community

It is currently May 26th, 2012, 9:45 pm

All times are UTC [ DST ]




Post new topic Reply to topic  [ 337 posts ]  Go to page Previous  1 ... 12, 13, 14, 15, 16, 17, 18 ... 23  Next
Author Message
 Post subject:
PostPosted: August 2nd, 2009, 10:03 am 
Offline

Joined: October 17th, 2006, 4:15 pm
Posts: 7502
Location: Australia
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.


Report this post
Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: August 2nd, 2009, 10:05 am 
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.


Report this post
Top
  
Reply with quote  
 Post subject:
PostPosted: August 2nd, 2009, 10:10 am 
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


Report this post
Top
  
Reply with quote  
PostPosted: August 19th, 2009, 9:45 pm 
I was just looking for moving windows between dual monitors. This tool works great without any issue in Windows 7 RTM.

Thanks.


Report this post
Top
  
Reply with quote  
 Post subject:
PostPosted: September 11th, 2009, 3:06 am 
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. 8)


Report this post
Top
  
Reply with quote  
 Post subject:
PostPosted: September 11th, 2009, 3:18 pm 
Offline

Joined: October 17th, 2006, 4:15 pm
Posts: 7502
Location: Australia
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


Report this post
Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: September 11th, 2009, 8:35 pm 
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. :D


Report this post
Top
  
Reply with quote  
 Post subject:
PostPosted: September 22nd, 2009, 4:16 am 
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?


Report this post
Top
  
Reply with quote  
 Post subject:
PostPosted: September 27th, 2009, 8:14 pm 
Offline

Joined: March 19th, 2007, 5:12 pm
Posts: 29
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.


Report this post
Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: October 27th, 2009, 5:13 pm 
Offline

Joined: October 27th, 2009, 5:04 pm
Posts: 2
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.


Report this post
Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: October 27th, 2009, 10:29 pm 
Offline

Joined: October 17th, 2006, 4:15 pm
Posts: 7502
Location: Australia
It's an intentional feature. I might add an option to move minimized windows, but I haven't had much time to code lately.


Report this post
Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: October 27th, 2009, 10:36 pm 
Offline

Joined: October 27th, 2009, 5:04 pm
Posts: 2
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


Report this post
Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: November 4th, 2009, 4:40 am 
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?


Report this post
Top
  
Reply with quote  
 Post subject:
PostPosted: November 5th, 2009, 10:44 am 
Offline

Joined: October 17th, 2006, 4:15 pm
Posts: 7502
Location: Australia
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.


Report this post
Top
 Profile  
Reply with quote  
 Post subject:
PostPosted: November 8th, 2009, 2:59 am 
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.


Report this post
Top
  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 337 posts ]  Go to page Previous  1 ... 12, 13, 14, 15, 16, 17, 18 ... 23  Next

All times are UTC [ DST ]


Who is online

Users browsing this forum: Bing [Bot] and 6 guests


You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Group