ID:155565
May 23 2011, 1:04 pm
|
|
Is there a way to use it but not call the Click() of the clicked target period?
|
May 23 2011, 1:27 pm
|
|
Not built-in, but it looks like it would be fairly easy to add. You could add an override variable to the GetClick datum (and set it in New()). Then under client/Click(), if clickwaiting.override is true, just return early before the ..() call.
|
In response to DarkCampainger
|
|
I came up with these 2 codes. Is either one correct?
client or client |
In response to Lugia319
|
|
Well, they both will always block atom.Click(). I was thinking of something a little more versatile:
/* Note that you shouldn't ever make changes to code within a library itself, so you should place this into a code file in your project. Now you can call GetClick() and set its override variable to true, causing it to block atom.Click():
GetClick(,,1) // Enable override (leaving the first two settings to default values)
|
In response to DarkCampainger
|
|
Thanks. Yeah I was really nervous about editing the library but I figured I could always re-download it if necessary.
|
I've updated the library with the functionality to do this. A true value for the new third argument to GetClick() (override) will suppress the normal Click() call.
This may potentially result in conflicts with other libraries if they also modify client/Click(), however. The change is also almost identical to DarkCampaigner's, but that's simply coincidental: I totally didn't even look at it. |
In response to Garthor
|
|
Awesome, thanks Garthor.
|
In response to Garthor
|
|
Saw this post while I was digging on a way to do something similar involving the interface file though (buttons to be more specific) and was wondering if its compatible with buttons, and if so, what does it return? The button ID / button text? If not, is it possible to be done and how.
Thanks in Advance! |