Been reading about (grumpy) people's problems transporting PowerPro to
Vista. Picked up a couple of tips from those posts but figured out and
found a few more workarounds myself.
Here is how I resolved some of the most annoying issues:
* Use {sinp} with *keys - as has been pointed out elsewhere. For
alt-tab I use *keys {sinp}{to taskbar}%{tab}, which works great.
* Use win.sendmouse instead of *mouse - as has been pointed out elsewhere
> This works fine unless you want to send modified mouse clicks (i.e.
clicks with Shift/Alt/Control held) - leastways I couldn't figure out
how to do this with sendmouse, so I'm now using the AutoIt plugin to
manage the part of the modifier keys (e.g. au.Send("{CTRLDOWN}")) and
win.sendmouse to do the clicking.
* Set master volume using NirCmd (a tiny freeware command-line tool,
see http://www.nirsoft.net/utils/nircmd.html). First I tried
Autohotkey but they haven't updated to Vista's new behaviour yet
(per-application volume settings) and the main workaround the AHK
helpfile offers (setting the scirpt file to compatibility mode for
Windows XP) hasn't worked for me with either Autohotkey or PowerPro.
What I haven't figured out yet is how to read out the current system
volume to use this information in my scripts but I've e-mailed the
NirCmd people and hopefully they will include this in their nifty tool.
OT:
By the way, you can also use the AutoIt plugin to send mouse clicks to
PowerPro's menus. In this way I was able to use middle clicks to
implement a third command for a menu item on top of the native left
click and right click options for menus. I use:
if (win.class(win.handlefrompoint(xmouse,ymouse))=="#32768")do
middleclick=1
au.LeftClick(au.MouseGetPosX,au.MouseGetPosY)
endif
The left click command for the menu item will branch off to a
different set of commands if the middleclick "flag" is set.
