 |
AutoHotkey Community Let's help each other out
|
| View previous topic :: View next topic |
| Author |
Message |
WindowPadFan Guest
|
Posted: Sat Apr 18, 2009 11:46 am Post subject: |
|
|
Lexikos,
I noticed that the windowpad script doesn't work in a remote desktop session. What could be the reason? Can you reproduce it on your system?
I have various other scripts, but they work fine.
Thanks! |
|
| Back to top |
|
 |
Lexikos
Joined: 17 Oct 2006 Posts: 4473 Location: Qld, Australia
|
Posted: Sat Apr 18, 2009 11:57 am Post subject: |
|
|
WindowPad interacts directly with windows. Windows within the remote desktop session (i.e. on the remote computer) do not technically exist locally - only the remote desktop client window.
Please clarify - is the script running on the remote computer or locally? Do the hotkeys have any effect? Which hotkeys are you using? |
|
| Back to top |
|
 |
WindowPadFan Guest
|
Posted: Sat Apr 18, 2009 12:52 pm Post subject: |
|
|
The script is running remotely. So I expected that the remote script would move the remote windows within the RDP screen. I used for example: CAPSLOCK-S. Does this make sense?
Thanks! |
|
| Back to top |
|
 |
WindowPadFan Guest
|
Posted: Sat Apr 18, 2009 12:54 pm Post subject: |
|
|
| Forgot to mention. None of the Windowpad have any effect. |
|
| Back to top |
|
 |
Lexikos
Joined: 17 Oct 2006 Posts: 4473 Location: Qld, Australia
|
Posted: Sat Apr 18, 2009 1:22 pm Post subject: |
|
|
| Try another hotkey, like #Numpad2. I recall CapsLock has issues with that sort of application. (I'm not sure if it was RDP, VNC, VirtualBox, etc.) |
|
| Back to top |
|
 |
WindowPadFan Guest
|
Posted: Sun Apr 19, 2009 12:01 am Post subject: |
|
|
You are, There is a CAPS (or win) key problem. That's unfortunate because my netbook doesn't have many key
Is this a not resolvable restriction? |
|
| Back to top |
|
 |
Lexikos
Joined: 17 Oct 2006 Posts: 4473 Location: Qld, Australia
|
Posted: Tue Apr 21, 2009 5:20 am Post subject: |
|
|
After some testing, it seems the problems I had seen with CapsLock were caused by WindowPad running on my local system (and the remote system). After uncommenting the following line in the [Exclude Windows] section of my local WindowPad.ini, the remote WindowPad works:
| Code: | | Window=Remote Desktop |
|
|
| Back to top |
|
 |
Guest
|
Posted: Tue Apr 21, 2009 9:05 am Post subject: |
|
|
| Yes, that seems to work. Thanks! |
|
| Back to top |
|
 |
wussboy
Joined: 20 May 2009 Posts: 3
|
Posted: Wed May 20, 2009 9:37 pm Post subject: |
|
|
| Registered just to say I've been using WindowPad for about a month now, and it has been immensely helpful. I feel sad for all the time I've spent lining up windows in the past, and now your program comes along and solves all my problems. Thanks! |
|
| Back to top |
|
 |
Eucaly61
Joined: 16 May 2009 Posts: 18 Location: TW
|
Posted: Fri May 22, 2009 12:50 pm Post subject: WindowScreenMove(P) with original window size |
|
|
some people (include me) would like to do WindowScreenMove(P) with original window size. Below is my modificarion on that
find below in WindowScreenMove(P)
| Code: | if (IsResizable()) {
w *= (mdw/msw)
h *= (mdh/msh)
}
; Move window, using resolution difference to scale co-ordinates.
WinMove,,, mdLeft + (x-msLeft)*(mdw/msw), mdTop + (y-msTop)*(mdh/msh), w, h |
replace with below
After that, give a 3rd parameter as "true"
WindowScreenMove, Monitor, WinTitle, FixedSize
| Code: | if (IsResizable() && !P3) {
wd := w*(mdw/msw)
hd := h*(mdh/msh)
} else {
wd := w
hd := h
}
x1 := mdLeft + (x-msLeft)*(mdw/msw)
y1 := mdTop + (y-msTop)*(mdh/msh)
if (x1 < mdLeft) OR (x1 > mdRight-40)
x1 := mdLeft
if (y1 < mdTop) OR (y1 > mdBottom-40)
y1 := mdTop
; Move window, using resolution difference to scale co-ordinates.
WinMove,,, x1, y1, wd, hd
|
_________________ Eucaly61's DIY World (Mainly in Chinese)
http://eucaly61.blogspot.com/search/label/AutoHotKey |
|
| Back to top |
|
 |
bidomo
Joined: 05 Feb 2009 Posts: 36
|
Posted: Wed Jun 03, 2009 3:38 am Post subject: |
|
|
Hi everyone!
Nice tool, is very useful in vista and multi monitor.
I'm adding a new function to Toggle muting the Mic In and the Line In (not messing with volume functions), it's just a test, I want to improve it as much as I can (took the code from an example script).
| Code: |
MicVolMute(P)
{
VA_SetMute(!VA_GetMute("7"),"7")
if VA_GetMute("7")
{
CustomColor = EEAA99 ; Can be any RGB color (it will be made transparent below).
Gui +LastFound +AlwaysOnTop -Caption +ToolWindow ; +ToolWindow avoids a taskbar button and an alt-tab menu item.
Gui, Color, %CustomColor%
Gui, Font, s25 ; Set a large font size (32-point).
; Make all pixels of this color transparent and make the text itself translucent (150):
WinSet, TransColor, %CustomColor% 200
Gui, Add, Text, cLime, Mic Mute ; XX & YY serve to auto-size the window.
Gui, Show, x850 y720 NoActivate
}
else
{
Gui, Destroy
}
} |
Is there a way to autoexecute this at the program start???
Of course, I'm gonna put the window (OSD) in another place on the main screen
Any help will be highly appreciated. |
|
| Back to top |
|
 |
Lexikos
Joined: 17 Oct 2006 Posts: 4473 Location: Qld, Australia
|
Posted: Wed Jun 03, 2009 3:53 am Post subject: |
|
|
What does it have to do with WindowPad?
For the answer to your question, see auto-execute section. |
|
| Back to top |
|
 |
bidomo
Joined: 05 Feb 2009 Posts: 36
|
Posted: Wed Jun 03, 2009 6:37 am Post subject: |
|
|
| Lexikos wrote: | What does it have to do with WindowPad?
|
Sorry, and thanks...
Well, I'm using WindowPad as my main script to control all of my Hotkeys, and I'm thinking in using it as library, but I'm trying my main attempts in every single (and useful) script, so in a near future, I can use them as functions...
Thanks for your directions! |
|
| Back to top |
|
 |
Max007 Guest
|
Posted: Thu Jun 04, 2009 6:16 am Post subject: Nice utility! |
|
|
| Thank you, i got my option window back! Nice work! |
|
| Back to top |
|
 |
wussboy
Joined: 20 May 2009 Posts: 3
|
Posted: Mon Jun 15, 2009 5:12 pm Post subject: NumberPad Zero triggers WindowPad when pressed quickly |
|
|
Hey all. I'm getting a weird behavior, and I don't know if it's WindowPad or AHK, but as WindowPad is all I use AHK for, I thought I'd start here.
WindowPad works as expected, however, when I am typing on the numberpad, if I press the 0 followed by another number too quickly, WindowPad will fire.
For example, if I type 210351 on the numberpad, my window will resize into the lower-right corner (as if I pressed Win + 3).
Any idea why that is? This behavior is a bit frustrating. Thanks! |
|
| Back to top |
|
 |
|
|
You can post new topics in this forum You can reply to topics in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|