Hi Scott, On Sat Oct 1 2016, Scott Rossi wrote: > The only method I've found to accomplish this > is to store all original rects before doing any > scaling and base all size computations on the > stored dimensions until the next resize event. > It requires a little effort, but it works.
I understand that your advice is correct but the script in the stack should (at least in theory) be exactly equivalent to store all rects and set controls position and size after resize is done. In practice, the script that I posted fails under some circunstances and I want to know which these circunstances are. Maybe, just maybe, there is a workaround to detect and correct these failures before setting the new size and position of all controls in card. Al On Sat, Oct 1, 2016 at 8:57 PM, Alejandro Tejada <capellan2...@gmail.com> wrote: > Hi All, > > Download the compressed stack "ResizeLivecodeGraphicsv01.livecode" > from this forum thread: > http://forums.livecode.com/viewtopic.php?f=10&t=28042 > > Some years ago, I made this live resizing script for my stack > PenTool http://www.capellan2000.000space.com/?i=1 > and now, I am trying to use this script for more general purposes, > like resizing all controls of an Interface... but after repeated > use, the script just distorts the size and position of all controls. > In the sample stack, these controls are vector graphics, but > could be fields, images, buttons, etc... > > Could you share some ideas about how we could make this script > mathematically more robust to resize all controls without distorting > their size and position after repeated use? > > Thanks in advance! > > Alejandro _______________________________________________ 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