Just a thought given other things I've experienced... That moveStack is likely getting executed twice an causing problems: once for the main stack and once for the substack (which doesn't override the moveStack handler and so it falls through to the main stack's script).
You could either: * put the moveStack handler in the card of the main stack * override the moveStack handler in the sub stack * check the short name of me to ensure it's the main stack To get rid of the lag, you may be able to lock the screen and unlock the screen after the stack moving is complete. It depends on when moveStack is called (after or before the move is complete). Jeff M. On Tue, Mar 2, 2010 at 11:56 AM, Richmond Mathewson < richmondmathew...@gmail.com> wrote: > I made 2 stacks: > > A main stack called "MAINST", and > > a substack called "SUBBY" > > and put this into the stackScript of "MAINST" > > on moveStack > put the right of me into RITE > put the width of stack "SUBBY" into WIDD > put (RITE + (WIDD/2)) into INN > put item 2 of the loc of me into UPP > set the LOC of stack "SUBBY" to INN,UPP > end moveStack > > play with it: > > http://andregarzia.on-rev.com/richmond/STUFF/MAINST.rev.zip > > there is a bit of a lagtime. > > sincerely, Richmond Mathewson. > > > > _______________________________________________ > 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