This explains a lot and solves the situation perfectly. But I didn't want you to apologize.
This was one of the first things I noticed in this community, what you say is heard and has immense weight (even if it is sometimes 4.2% incorrect). There are impressive landmarks here (or in forum), to specify some: A "Did you think about this"-line of Craig, a regex-one-liner of Thierry, a "Hmmmmm"-line of Mark-W., a "little stack" of Bernd, a "Hi"-shortliner of Mark-Sch., a spikey line with two smilies of Klaus, a "FWIW" note of Richard, an opening "welcome" by Simon or a closing "nagging" by Richmond (I have to stop now or nobody will read to end). Your words are more than landmarks, rather seen like a monument in front of a train station. I think you should be *very* proud of this. And also, let me say this again, be very careful with this. > hh wrote: > > Please be cautious with your direct or indirect "rating": > > jacque wrote: > Apologies if it sounded like I was giving a "rating." Your method, and > the others, will work fine for most stacks. I only meant that in this > particular case, it won't. > > I have a suite of hundreds of stacks with tens of thousands of cards. > The stacks are created automatically by a building tool based on the > contents of text files, and some cards require specific plugins I've > written. The plugins need to work independently of the larger system. > > That's because there is a backscript which is the main heartbeat of the > app, and it changes the state of every card in both openCard and > preOpenCard handlers. Whatever a group sets up is likely to be undone if > it uses any of those messages. That's why I need a message that isn't > included in the backscript. The same thing would apply to a frontscript, > which would change the group state first, and then the backscript would > undo those changes. > > I didn't mean to be critical, just explanatory. As I said, any of the > methods various people have suggested would be good solutions most of > the time. _______________________________________________ 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
