06-26-2006, 03:06 PM
Hi! remember me?!
Well I have finally got around to actually using the Freehand zooming utility you helped me to write. So one issue has come up:
Although I can now do a repeated CTL+Wheel F/B without ever releasing the Control button, if I modify the Control button using a SHIFT or ALT then I get back to the same situation, i.e., I first have to release the modifier button in order to get QM to recognize the it at the next mouse wheel action. If I do not release the button, then only the CTL is recognized and the macro servicing CTL+Wheel is invoked.
So, again, how do I get CTL+ALT Wheel to work continuously without taking my finger off the ALT button?
tia
Avraham
Well I have finally got around to actually using the Freehand zooming utility you helped me to write. So one issue has come up:
Although I can now do a repeated CTL+Wheel F/B without ever releasing the Control button, if I modify the Control button using a SHIFT or ALT then I get back to the same situation, i.e., I first have to release the modifier button in order to get QM to recognize the it at the next mouse wheel action. If I do not release the button, then only the CTL is recognized and the macro servicing CTL+Wheel is invoked.
So, again, how do I get CTL+ALT Wheel to work continuously without taking my finger off the ALT button?
tia
Avraham
amakeler Wrote:[quote="Gintaras"] This version does not use keys, and Ctrl should not interfere.
BINGO! IT WORKS!!!
I don't know whether to kiss you or to strangle you - I have been working on this for ages.
Question: in this code segment, what are the commas at the start of the lines?
if(action)
,s.getwintext(handle)
,int i=val(s)
,if(action>0) size=i+size
,else size=i-size
Were they really tabs? (No, I didn't use that part of the code.)
Question: The 0 in s.setsel(0 handle) is a null format specifier? You don't need commas in QM API?
Question: In the parameter list in the statement
int handle=id(432 "FreeHand")"
wouldn't it be more appropriate for the (parent) app name (i.e., "FreeHand") to come first (i.e., on the left) before the child handle number rather than the other way around.
Btw, that QM GUI feature for displaying the Win ID numbers of app controls under the mouse is really great.
Btw, I noticed that online help did not always represent how a feature actually worked. Maybe it's a bit old here and there.
The name Quick Macros, when you get to know it, doesn't really do justice to your app. I would suggest "Macro Manager". But maybe Quick Macros is more attractive from a sales point of view.
Ok, now to get back to my real job and carry on earning a living...
Thanks,
Avraham