When you go to another card, lots of things happen before and after the go. By way of example, Closecard gets sent to the curent card, but before that close field gets sent to any field that you are in that has been edited, etc. Before the card opens, it gets a preOpenCard. So don't think that by going to a card, that command gets executed first, then all the other stuff happens. That isn't how it works.
The best way to tell what is going on is to turn on message watching, then set a breakpoint right at the first and then step through every line of code. Then you can review the message watcher and you can see all kinds of messages are flying around that you were unaware of. Bob S > On Oct 31, 2017, at 06:09 , Pyyhtiä Christer via use-livecode > <use-livecode@lists.runrev.com> wrote: > > When in a script you issue a command > > go card "xyz" > > does the next command line of the script get into execution before the "go" > has been completed? > > Is it comparable to the "move" command, where this is true, with the > additional statement "without waiting"? > > Is it possible to find a delay in the "go" command if you for example go from > card 2 to card 28 and there are many objects in the cards in between? > > The fact is that the behaviour varies, same code at different times in some > cases looks like an action is tried to be done for the card going out. > > > Christer Pyyhtiä > chris...@mindcrea.com > > > _______________________________________________ > 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
