I made some enquiries from the team on this, and I'm told: You can only profile a stack, not an individual handler. It profiles the top stack when you start the profiler, so you just have to make sure the stack with the resizeStack handler is the top stack, then start the profiler.
I hope this helps! Regards, Heather Heather Laine Customer Services Manager LiveCode Ltd www.livecode.com > On 5 Mar 2017, at 01:07, Ralph DiMola via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Both the Remote Debugger and Script Profiler are exciting. There's only one > of me so I went for the script profiler first. Looked at the LC lesson and > it seemed simple enough... Enable, do some stuff in your stack and the > disable. I did that and the Profiler screen pops up but it's empty. Am I > missing something? How do I set the message/handler level to be profiled? > Say I want to see how long it takes to resize the stack. I first profile the > script in the resizestack handler but not any deeper. I then see that one of > the handlers called in the resizestack hander takes too long so now I want > to profile just that handler. > > Has anybody got this working? > > Thanks > > Ralph DiMola > IT Director > Evergreen Information Services > rdim...@evergreeninfo.net > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
