On 2015-10-14 10:21, Monte Goulding wrote:
Don’t both of these issues disappear if you create a stack view object instead of group scalefactor? Given a stack which already has a scaleFactor? Object rects remain relative to the stack whether the stack is presented as a window or in a view. From the perspective of the stack with the window it would just have a single view object which has a stackName and a rect.. perhaps some other stuff like visible etc...
Yup - if you have a 'stackview' control - then the problem goes away because you have a nice clear dividing line between objects in one co-ordinate system compared to the other.
We'd probably want some explicit syntax for working out the rect of an object in a stackview, from the point of view of the stack containing the stackview; and also some means to communicate from the embedded stack to the host view... However, perhaps both of these things are unnecessary - the stacks could just as well communicate by sharing a common library.
Basically, there aren't really any difficult technical problems if you limit stackviews to being 'the ability to display a stack in a subpart of another stack, rather than a window' with no more integration beyond that, other than them being stacks.
Mark. -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Everyone can create apps _______________________________________________ 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
