AutoHotkey Community

Hey, it works! You're a star, many thanks for your help.

All it needs now is to be made into a toggle (Just kidding, I understand that means variables and the like, takes loads more work, it's fine as it is.)

Have a great day!

Alternatively, you could bind a separate hotkey to =WPM R,R, which restores the window to the last "non-WindowPad" position and size. I use (Capslock & ) LAlt=WPM R, R0, , 1.0, which toggles between the full height of the screen and the original position and size (width is not affected).

I really admire this script! It´s very, very helpful.

BUT i´ve got a problem with my Citrix App´s
I can´t move them, with the exception of fixing the window size. (That shouldn´t be the solution)

Otherwise the seamless window isn´t detected correctly by the script.

That´s my AutoIt3 Window Spy Output:


How do I have to proceed further to manage my Citrix App´s with this wonderful script

I just found this script and this is useful. What about throwing a window (drag-and-drop quickly) acts the same as the hotkeys (Windows key + numpad numbers) depending on the direction of the thrown window?

Excellent script. However, trying to run a command through the command line as indicated in the documentation does not seem to work. For example, I tried running the following


This is the error I got

The same error comes up when I try to run any other command as well.
I tried to debug the script, but I don't understand what 'aName' is; it is not defined/assigned to anywhere.

Since there is a space between the command and args, use quote marks as indicated in the documentation.

That fixed it, thanks!

I did read that line in the documentation but I thought it applied when an individual parameter had spaces... because your example for this contains the parameter "My Window" Though I see now that the documentation via comments in the actual code is much clearer. Anyways, thanks so much, and maybe you'd wanna make the documentation in the HTML help file regarding this point clearer as well.

But shit how awesome is your script! I mean it can be used as a standalone script, as a library, and also through the command line! The kinda code you write helps us all learn how to design/write code. (I was thinking of using it through the command line since it wouldn't stay persistent in memory, though I do plan to be using it all the time; do you think the regular loading into memory defeats the purpose of not having it running all the time?)

Also, could you explain how the aName thing works, or tell me where I could look that up. The only thing I could find in the AHK documentation containing aName and aParams is in the section on Objects and that also doesn't explain what they are

Thanks for all you great scripts !

Exactly what is the purpose of not having it running all the time? Unless your system is severely low on memory, you're probably just wasting (CPU) time.
aName is set by RegExMatch based on the UnquotedOutputVar parameter (which is a) and the (?<Name> ... ) sub-pattern in the NeedleRegEx parameter. Look for "RegEx" in the help file index. If you have any questions, please post them in the Ask for Help forum.
In that case, I used the "a" prefix to indicate that they are arguments of a function; it is a convention I sometimes follow, picked up from the original AutoHotkey source code. In WindowPad, "a" is just an arbitrary prefix, which I may or may not have chosen loosely based on that same convention. I could just as easily have used "m", short for "match".

I think the previously posted idea of throwing a window to dock it to the end of the screen is good. I hope it is implemented.

Thanks for your patient explanation Lexikos. Yeah, "ask for help" is where I normally post when I have questions, and I posted here only since my post was in continuation of the last one. But thanks for pointing me to the regex section of the help file. I would have never been able to figure out how the aName variable was magically getting a value otherwise

Great little program. I am trying to make a version that is not dependent on the numerical keyboard, and have added the following hotkeys to the ini file.

However, I lack the option of calling WPM with just x parameter, e.g.:



With these in place, you basically have the same functionality as #Numpad1-9, excluding #Numpad5.

Any suggestions or help with this is much appreciated.

Hi there,

I refactored the script written by Lexikos and added a few features.

During refactoring I splitted the single file in two files: the first file containing mostly the main program (File WindowPadX.ahk), the second file mostly containing helper functionalities and the "actions" which can be performed (File WPAX.ahk). During refactoring I homogenized the function names and added some consistent documentation ...

Functionality I added:

• Restricting mouse movements to a single monitor (mouse can not leave this monitor)
• Center mouse on a given monitor (i.e. easy move mouse from monitor 1 to monitor 3 ...)
• Visually locate the mouse (if you can't find it ...
• Functionality to minimize all windows on a given monitor (something like standard windows functionality for WIN-M (Minimize all Windows) - but monitor specific (Minimize all windows on monitor where the mouse is)
• Simple window functionality to toggle "AlwaysOnTop" or "Roll/Unroll" for a given window
• Some simple Restore-Mechanism: on program exit, some properties are restored (for example: if the "AlwaysOnTop" flag is set on program exit, it will be removed)
• ...

After all this Work I renamed the original WindowPad to WindowPadX.

I released my modifications on Github. You can download different versions of my development here.

Have fun ...

P.S: It still needs some enhancements

_________________________

www.palatialsoftware.com/plumb

Does everything here with some additional features, might be worth a look.

I don't see where plumb supports special multi-monitor commands or can do anything else what WindowPad offers in this field.

Plumb seems to be designed (almost only) for tiling windows on one screen (I failed to apply the tiling on my second monitor - I must admit, I tried only for a few seconds ...) Concluding from this, I think Plumb is more comparable with bug.n - Tiling Window Manager than with WindowPad. (I cannot say much about bug.n - as I do not use it ...)

I personally don't like and use automatic windows tiling, so there's no need for me to investigate this further.

hoppfrosch, Lexikos,

I just checked out the version put out by hoppfrosch and noticed that some window transitions/moves don't respect the "restore" position. I don't know if the original from Lexikos has this issue also.

I updated WPXA_MaximizeToggle() to account for a restore position. I'm not sure if I really want to save a maximized restore position or not but at least this will not lose a previously recorded restore position if you Maximize the window using Win-+ for example. I also made a similar change to WPXA_MoveWindowToMonitor() to account for the restore position.

_________________
SJKeegs