QuickTime conundrum

[Richard Gaskin]

I filed a bug report this weekend for this anomaly with QuickTime and 
menus - Windows only:

   Hold the mouse down over the menubar to pop down the menus,
   esp the submenu in Edit.  When a QT movie is assigned to
   the player the movie flickers.  If you play with it enough
   you'll get in some sort of loop that consumes 100% of CPU
   and is hard to break out of.
<http://support.runrev.com/bugdatabase/show_bug.cgi?id=2692>

There's a sample stack there which exhibits the behavior, but it's easy 
to make one:

Just put a menu group in a stack, then put a player there.  Give one of 
your menus a submenu -- the more items the better.  Then put a player on 
the card, assign it a movie (the longer the better) and try to select 
something from the submenu.

What happens appears to be some sort of loop in which the menus (esp. 
the submenu, as it's much more noticeable there) is fighting with QT for 
redraw time -- whenever you drag the mouse over another menu or submenu 
the player flickers, and the menu takes a long time to draw.  Drag 
across multiple menus and you may well trigger a loop that you may need 
to force quit to get out of.

I just tried my experiment using Rev's menus, and the same thing happens:

1. Make a new stack
2. Put a player in it
3. Assign a movie to the player
4. Drag the mouse across the Rev menubar and down some menus to '
    bring up submenus -- I got a freeze

I'm hoping to find some magic combination of properties to help 
alleviate this.  Unfortunately I must have the player's controller 
available, so simply turning on the player's alwaysBuffer -- while it 
does improve things -- won't work in this app.

Any clues?

Alas, it seems half of my life is consumed with anomalies related to 
QuickTime.... ::sigh::

--
  Richard Gaskin
  Fourth World Media Corporation
  __________________________________________________
  Rev tools and more: http://www.fourthworld.com/rev