Bob, You're missing the point. Everything works exactly as coded when the stack is not run as a plugin. The problems I've described only occur when the stack is run as a plugin. It's mtto anyway becasue I'm not executing that code anywhere now since I that property only needs to be set once. Pete lcSQL Software <http://www.lcsql.com>
On Wed, Aug 29, 2012 at 1:19 PM, Bob Sneidar <b...@twft.com> wrote: > Why do it there? Can you put it in the opencard handler of the script of > the first card? I have found that some things don't work as expected in > preOpenstack. I would imagine changing the properties of an open stack > would cause problems, since the stack is not technically "open" yet. If you > try to change the property of a stack that is not open, (assuming LC knows > where it is) LC will attempt to open it. Wouldn't that trigger preOpenstack > again? > > I'm just fishing here. > > Bob > > > On Aug 29, 2012, at 11:18 AM, Peter Haworth wrote: > > > Thanbks Mark. SOunds like Powedebug would be a great hep - where can I > get > > it? > > > > But I'm still puzzled why setting the liveresize of a stack would cause > all > > these issues - that doesn;t seem to fit any of the situations where debug > > doesn't return errors. All I know is that without that statement, all > > works fine, with it things go haywire. > > > > Pete > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
