Sorry for the late response, but thanks for the shoutout. I'll also mention that some time ago I put a fair bit of effort into enabling Navigator to behavior-ify any set of controls, automatically extracting their built-in code to script-only-stacks. I did it as part of the migration of Navigator to SOS behaviors. I haven't checked to make sure, but I believe *all code* in Navigator is a SOS-behavior; and I did that automatically from a no-behaviors standing start with a simple command in Navigator itself. The end result is that there can be any number of Navigator windows without any duplication of code at all. Previously I had built Navigator with three built-in copies, at the cost of making it three times as large. That wasn't such a terrible thing, but I did find that anything beyond three copies eventually broke (no idea why). Since migrating 100% to behaviors, I've tried, I think, having ten copies open with no problem.
Disclaimer/warning: I wrote that code five years ago and haven't looked at it since. No one has told me it doesn't work, but I only used it the one time on Navigator itself. So work on a copy, please. gc On Wed, Jun 22, 2022 at 1:25 PM Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Well then Navigator is for you! If an object has a behavior and no script > of it's own, it's color in the list is green. If it has a script but no > behavior, it's color is blue. If it has both, it's purple. Simply double > clicking an object opens it's behavior script if it has one, and it's > native script if it doesn't. > > You don't have to keep track of anything anymore. > > Bob S > > > > On Jun 22, 2022, at 12:41 , J. Landman Gay via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > I find that too many behavior stacks make it difficult to keep track of > where things are. But the primary downside is that script-only stacks don't > work with remote debugging. That's a big drawback for me since most of my > apps these days are for mobile. I do use behaviors quite a bit, but I put > the scripts into buttons so they can be debugged remotely. Or maybe you > mean you use regular stacks for behaviors? Those would work. > > > > The switch construct is way more flexible than if/then and much cleaner > to read and track. I use them all the time. They're especially useful when > you want to group several conditionals. What don't you like about them? > Just curious. > > > > -- > > Jacqueline Landman Gay | jac...@hyperactivesw.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
