I can't seem to duplicate your problem, but I have created a similar setup
that works without a problem. I have a couple of questions about what you've
done; maybe in answering them, you will find the problem.
> -----Original Message-----
> From: Michael Walas [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 24, 1999 10:47 AM
> To: [EMAIL PROTECTED]
> Subject: btns don't like each other
>
>
> I have an option style navigation btn (no submenus) on each cd of my
> stack. As the user adds and names new cds to the stack, this btn's
> contents is updated with the new name of each new cd.
Is this button grouped? Or do you have a separate button on each card with
the same name and the same script? If it's grouped, then I don't think you
want to be referring to it as "cd btn"; just call it "btn". If the button
appears on every screen, then I would think you would want to have it
grouped for efficiency's sake.
>
> The script:
> on mouseUp
> put the value of selectedline of cd btn "Go To" into gowhere
> #lines here use the random function to generate a visual
> effect for the
> cd transition**
> go cd gowhere
> end mouseUp
Is this script in the button itself? If so, why refer to the button by name
when you could just say "of me"? if the script is elsewhere, then you
probably are creating a message-passing conflict when you add the second
button. (See my further thoughts on this below.)
>
> As soon as I add a different option btn (with submenus) with
> a menuPick
> handler, the script above doesn't work (the value of
> selectedline of cd
> btn "Go To" returns nothing) I know I could use a menuPick handler in
> the "Go To" btn but when I do, **the visual effect on going to the
> desired cd occurs twice.
I couldn't figure out how to create an option button with submenus. Is it
really an option button, or is it a pulldown menu button? And if that's the
case, is your navigation button also pulldown style rather than option
style?
> The script in the 2nd option btn : (This 2nd option btn
> (with submenus)
> is part of a group on the cd.)
> on menuPick lookhow
> set the itemDel to "|"
> put item 2 of lookhow into lookhow # item 2 is the submenu item
> if lookhow = "rectangle" then set the style of fld 1 of me to
> rectangle
> # many more if lookhow =
> end menuPick
> The script for this 2nd btn works flawlessly - it just won't allow my
> navigation btn to operate. Why won't the two scripts co-exist?
Where is this menuPick script? If it's in the button itself, saying "fld 1
of me" doesn't make sense because "me" is the button, not the card or the
group. If the menuPick script is somewhere else, maybe that's the problem,
because your other button also sends a menuPick message when you make a
selection, and since you haven't written a handler to catch it, the menuPick
handler for button #2 catches it, but it makes no sense with the values from
button #1, so nothing happens.
I recommend the following:
- Put each button in a group. If they always appear together, you could put
them in the same group, then place this group on every card that needs it.
- Put the script for each button in the buttons themselves, rather than
anywhere else.
Hope this helps!
--Marni
----------------------------------------------------------------------------
--------------------
The views and opinions expressed in this email message are the sender's
own, and do not necessarily represent the views and opinions of Summit
Systems Inc.
