Hmm, this is what "the stacks" returns for me: /Users/gcanyon/Desktop/nav tester 0.004608
/Applications/LiveCode 9.6.8.app/Contents/Tools/Toolset/palettes/script-editor/revscripteditor.rev 0.272558 /Applications/LiveCode 9.6.8.app/Contents/Tools/Toolset/palettes/tools-palette/revtools.livecodescript 0.440798 /Applications/LiveCode 9.6.8.app/Contents/Tools/Toolset/palettes/dictionary/revdictionary.livecode 1.72743 /Applications/LiveCode 9.6.8.app/Contents/Tools/Toolset/palettes/menubar/revmenubar.livecodescript 0.421698 /Users/gcanyon/Desktop/nav tester 0.00453 0.007308 /Applications/LiveCode 9.6.8.app/Contents/Tools/Toolset/palettes/inspector/revinspector.livecodescript 1.565991 /Users/gcanyon/Documents/My LiveCode/Plugins/Navigator.rev 1.348666 Note the super long times for the dictionary, the inspector, and navigator, the mediocre times for others, and the super fast time for the stack actually running the code. I'm on an M1 mac running 9.6.8 On Fri, Sep 23, 2022 at 6:48 AM Craig Newman via use-livecode < use-livecode@lists.runrev.com> wrote: > Something weird happened to my post. > > I modified your handler to access only those stacks that appear when > calling the function “the stacks”. In all those cases, the return time was > only a few tenths of a second. > > But “revNaviigator” does not appear on that list. So there must be a > longer pathway for LC to find a stack that certainly must be in memory, but > that does not appear in the “stacks” list? > > Craig > > > On Sep 22, 2022, at 3:58 PM, Geoff Canyon via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > I was testing something for Navigator and found the following: > > > > put the long seconds into T > > repeat 10000 > > get there is a card 1 of stack "untitled 1" > > --get there is a card 1 of stack "revnavigator" > > end repeat > > put the long seconds - T into T > > put T > > -- puts 0.005 or so > > > > put the long seconds into T > > repeat 10000 > > --get there is a card 1 of stack "untitled 1" > > get there is a card 1 of stack "revnavigator" > > end repeat > > put the long seconds - T into T > > put T > > -- puts 1.2 > > > > Why in the world would it take over 200x as long to identify that there > is > > a card 1 of Navigator vs. a random stack I just created? > > > > I just checked and: > > stack "message" -- over 3 seconds -- a second run was 0.4 > > stack "revdictionary" -- 1.5 seconds > > stack "home" -- 0.02 seconds > > > > I ran it across everything in the environment and got results from under > a > > hundredth of a second to over a second, with stacks pretty smoothly > across > > that range. No clue what's causing it. > > _______________________________________________ > > 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 > _______________________________________________ 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
