If you are in the script editor window, you can right click on the name of
any handler and select "Go to definition" to display the handler in another
tab in the script editor. Of course that means finding a call to the
handler you're interested in or just adding a line of code somewhere that
call
> On 6 Jun 2015, at 21:51, Terence Heaford wrote:
>
> I simply used Find & Replace in the IDE, input the handler I was searching
> for and it took 60 seconds to parse the stack.
Please note this is the Find & Replace that is NOT in the Script Editor? The
Find & Replace in the script editor t
> On 6 Jun 2015, at 18:05, Richard Gaskin wrote:
>
> I would be interesting to learn more about the areas where Terence has found
> it slow to do these sorts of things.
I simply used Find & Replace in the IDE, input the handler I was searching for
and it took 60 seconds to parse the stack.
Richard wrote:
>
> I haven't seen a language with a built-in function for finding orphaned
> handlers across a code base
I always get jealous when I see the Java collegues work with eclipse…
Best,
Malte
___
use-livecode mailing list
use-livecode@list
Mike Kerner wrote:
> On Sat, Jun 6, 2015 at 9:29 AM, Terence Heaford wrote:
>
>> What made me ask this question is because of the amount of time
>> it takes the IDE to find and list methods that I ask it to find.
>>
>> This would be an acceptable way of working if it wasn't so slow.
>
> I'm not t
I'm not trying to be a smart-ass with this, so don't take this as some
dismissive remark. What I really want is to get everyone who gets
interested in one little piece of the IDE to crack the lid on it and work
on it.
The easiest way, IMHO, to do what you are suggesting, is to add some code
to th
What made me ask this question is because of the amount of time it takes the
IDE to find and list methods that I ask it to find.
This would be an acceptable way of working if it wasn't so slow.
All the best
Terry
> On 6 Jun 2015, at 13:42, Mike Kerner wrote:
>
> No, and that would be quit
No, and that would be quite a bit harder, here, because the structure is
different: "Send", "Dispatch", and "Do" will all let you build a call,
dynamically, to any handler in any stack. Plus, since everything is
event-driven, one would have to determine everything that is user-event
driven, and i
