2009/9/18 Richard Gaskin <ambassa...@fourthworld.com> > > Very interesting bug you stumbled across there. Oddly enough, I can't > reproduce it using: > > put the long id of btn id 1008 of stack "b" >
Unfortunately not. I can't track it down - think I'll throw in an exectutionContexts so I can figure out when the bug gets triggered The weirder part of that report was the part about behaviors being > disconnected even though the behavior reference was apparently correct: > > Then I issued "set the behavior of grp 1 to the behavior > of grp 1" and everything started working again across > multiple stacks. > > If the behavior is a valid reference, what would cause it to go bad? > I've not had this in a while - so I am not sure. Part of the problem was also my fault in that if a behavior is set to a stack, and that stack is not in memory then obviously the reference fails. Some of the behaviors were in stacks with destroystack = true and in those case where the stacks had no entries in the stackfiles the behavior failed. But why the above fixed things in early 3.5 I never figured out. _______________________________________________ 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