On Wednesday 02 October 2002 05:24 pm, John Hinsley wrote:
> Damn! This actually looks
> like a bug, but I'll see if I can come up with a workaround for the
> tutorial over the weekend. With any luck, someone will come up with
> a fix so I don't have to!

Sounds like the "targetOffset" stuff acting up. The Morphs remember=20
where the event that activated the menu happened; in the case of=20
scripting, I'm not sure where that would be.

Actually, in the particular case of making a button that invokes a=20
menu item (like "find"), using scripting is overkill. You can make=20
buttons from any menu item by dragging (or duplicating) the item and=20
removing it from the menu:

* red-button click on the book menu button
* blue-button click on the "find" menu item; the menu's halo comes up
* one more blue-button click on the same menu item moves the halo to=20
the menu item
* now use the duplicate (green) or grab (black) handle to get the=20
"find" item.
* It will become a button, which you can re-color, re-name, etc. and=20
embed in your book prototype page.

This doesn't work so well with updating menu buttons (they don't=20
update), but generally is quite useful.

--=20
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE