Windows menu bars

[Ron]

Hi Jacque

You are right about your approach because you are using multiple cards  
on one window. In my case I had multiple windows in the same app. So,  
like you, I used empty buttons, a single backscript and one menupick  
handler. But because there are different windows, I switched to  
behaviors once they became available.

Thanks
Ron
On Jan 28, 2010, at 4:23 AM, zryip theSlug wrote:

> 2010/1/27 J. Landman Gay <jacque at hyperactivesw.com>:
>
>
>> What I've done is to have zero scripts in the menubar at all. It's  
>> just a bunch of empty buttons. All the stacks are run by a
>> single backscript, and there is one menupick handler in there with  
>> all the menu items in it (it's a pretty short menu.) That means >  
>> there is only one handler to manage.
>
>> I thought about using behaviors, but I didn't see an advantage to  
>> it in this situation. Would there be one?
>
> Behavior or other way to not have to repeat the same code. No
> particular advantage with it here. Just I had it in head when I wrote.
> ;)