It seems I messed up my search of this list - when I did it again, I did find some correspondence about this and a possible workaround from Ken Ray for dealing with the problem as it occurs in 'standard' dialogs, such as the 'answer' one, although I haven't followed it all up yet.
OTOH that conversation makes me think much more firmly that it's a bug: why on earth shouldn't one be able to set the location of **any** stack? Why does the engine bother to fight against it? In fact, why can't we say open stack "MyStack" at <location>? Graham Earlier, I wrote: > Perhaps I missed this in the documentation, but it seems to be an anomaly: > > If I have a mainstack with a substack "MyTest", then if I do > > set the loc of stack "MyTest" to the screenLoc > open stack "MyTest" > > sure enough the stack appears at the screenLoc; but if I change the statement > to: > > open stack "MyTest" as modal > > the stack appears elsewhere on the screen! As I am growing my own dialog > boxes, this is mighty inconvenient. The only way I have found to get round > this is to have an OpenStack handler in the substack itself which contains > the statement: > > set the loc of this stack to the ScreenLoc > > then it works. > > Am I doing something wrong, or is it a bug or is it a (very strange IMHO) > feature? > > Graham _______________________________________________ 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
