I've found a workaround to the problem of slow opening of card 2, as follows: a. Originally, card 1 (the opening screen) had a "Start" button with the script going next to card 2 b. Make this opening screen card 2 c. Make card 1 a dummy card d. Add to the stack script: on openStack set lockcursor to true set cursor to watch go to card 2 set lockcursor to false end openStack
This seems to do the trick, but admittedly it's a roundabout way that does not explain the original problem. Steve Goldberg In a message dated 12/18/06 1:00:47 PM, [EMAIL PROTECTED] writes: > > > > I know this issue has been raised in the past, but bring it up once more > > with > > > the hope that someone may have a resolution. The problem is that after > > > using my Mac to create a standalone and then transferring the Windows > > standalone > > > version to a Windows computer, the intial opening screen may open in a > > > reasonable time, but on trying to go to the next card with a simple "Go > > Next" command, > > > there is a significant delay in going to that card. After going to > that > > > second card, the program performs quickly in going from card to card. > > Why is > > > there this delay and how can it be avoided? > > > It doesn't seen related to whether or not there are any substacks, since > > the > > > problem exists when there are no substacks and also exists when the size > > of > > > the stack is relatively small. > > > It has been suggested that perhaps it takes some time for the program to > > > fully load. However, I tried the following unsuccessfully: > > > a. I tried waiting some time before clicking on the "Go Next" button, > but > > > there still was a delay in going to that second card. > > > b. Considering that there may be a delay in loading the program fully > > until > > > one makes the move to that second card, I wrote the following script: > > > > > > On openStack > > > set lockscreen to true > > > go next > > > go prev > > > set lockscreen to false > > > end openStack > > > > > > However, the delay persists. Any ideas? Thanks. > > > My problem does not seem related to whether there are images or sounds on > card 2. It is the same problem even if there are no images or sounds within > the > standalone. Also, I cannot see it being specific to any other content on > card > 2 since the problem exists in a variety of standalones which are quite > different. Is this a known problem in Revolution? If not, perhaps it's > something about my Windows computer (which tends to run slowly in general) > rather > than Revolution. My concern is that I need to distribute these standalones > to > Windows users and it can be frustrating waiting for that second card to > open. > I've tried to alleviate the problem partially by setting the cursor to watch > until the second card loads. > Steve Goldberg > > _______________________________________________ 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