Stylistic question.

[Bob Sneidar]

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 at 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 | jacque at hyperactivesw.com