I have a stack with buttons to cards with large graphics in each card. There are 500 graphics being displayed one at a time. When I use "go stack" it sometimes sends one of the 'open' messages twice!!! This did not happen when the number of graphics was smaller. SO during development (as I added more cards with graphics) the 'go stack' which calls 'preOpen' and 'Open' card eventually started a strange behavior of opening the new stack but jumping back to the stack that the button was on.
I think my problem is related to yours via the 'openCard' message path.


Hope we can figure this one out.

TOm

On Feb 8, 2004, at 12:51 AM, Alex Rice wrote:


On Feb 7, 2004, at 12:22 PM, Jeanne A. E. DeVoto wrote:


Increasing the delay might work, as a workaround.

Oh god. Is this an engine bug or an IDE bug? Surely "go next" isn't broken?


I can replicate the problem by doing this:

1) create a bunch of cards with _large_ referenced images (set the filename of image to ".../whatever.tif")
2) don't save the stack yet!
3) put this in the mainstack to keep track of where you are:


on openCard
 put the number of this card
end openCard

4) command-3, command-3 etc.

5) Forget it, now the problem isn't happening. It was a moment ago. I hate this intermittent kind of bug.

--
Alex Rice | Mindlube Software | http://mindlube.com

_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution



Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541

_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to