Richard,
Timely question. I'm using a cascading menu/button to give the user the
option to select a video file which could reside in any of three
folders. Each folder has one or more subfolders. For example:
Video Group 1
Animals
Elephant.mov
Tiger.mov
People
Richard.mov
Video Group 2
Cars
Ford.mov
Chevy.mov
etc...
The advantage of this approach is it takes up very little room on the
screen (i.e. just one small button), but provides easy access to lots of
files.
I was about to submit this bug report (this functionality worked two
days ago, but not now), but I'd like others to test it first. I could
only test it under XP.
Start with a new stack in Media.
1. Create a popup button. It will come with three lines of data in it.
2. Run it in a browser. Should function normally... meaning, you can
select one of the three items.
3. Go back and enter this into the message box:
put return & tab & tab & "choice x" after line 1 of btn 1
4. In the development environment, "choice x" should now appear as a
sub-choice of the first menu item, and you should be able to select it.
5. Run it in a browser. When I test this now, it is no longer possible
to select any menu item, let alone "choice x".
Is that what others are finding?
Thanks.
Richard Miller
Richard Gaskin wrote:
Richard Miller wrote:
I've discovered some other significant (for me) change to the runtime
environment in the past few days. A traditional cascading menu (built
with the menu builder).... which worked fine yesterday during
runtime... no longer works today. The menu (which I dragged to the
center of the stack so it functions as a button with cascading
selections), depresses OK. The list of hierarchical selections show
up OK. But any attempt to actually make a selection fails.
At last I've found someone else who uses cascade menus!
Cascade menus were originally added as part of the old stack-based
menu system, which few people use anymore now that we can use the
textual contents of menu button as menu items without having to build
a stack for those.
But cascade menus remain very useful for another purpose, as flyout
menus. Adobe and many others place such menus at the upper-right of
their palettes, and they're useful in other contexts as well.
But unfortunately, the behavior of cascade menus differs from others
in that most menus let you click and release and the menu stays up
until you either select one of its items or click away from it, but
cascade menus only appear as long as the mouse is down.
Also, while most menu styles render their menus using OS routines,
cascade menus draw using the built-in emulated appearances, giving
them a non-standard look that compounds the non-standard behavior.
There are workarounds for this, but they're not straightforward to
implement and would certainly throw off the newcomer.
Jacque has noted this in the RQCC, and I've amended her request with
additional notes:
<http://quality.runrev.com/qacenter/show_bug.cgi?id=1338>
Richard, what do you use cascade menus for?
--
Richard Gaskin
Fourth World
Rev training and consulting: http://www.fourthworld.com
Webzine for Rev developers: http://www.revjournal.com
revJournal blog: http://revjournal.com/blog.irv
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
