Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Why mouse wheel F/B ok, but with <CTL> first needs rel
#19
[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


Messages In This Thread

Forum Jump:


Users browsing this thread: 1 Guest(s)