Yup. Otherwise you incur generational loss. Like editing and saving a JPEG
multiple times on high compression.
> On Oct 1, 2016, at 18:39 , Scott Rossi <sc...@tactilemedia.com> 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
> Scott Rossi
> Creative Director
> Tactile Media UX/UI Design
>> On Oct 1, 2016, at 5:57 PM, Alejandro Tejada <capellan2...@gmail.com> wrote:
>> Hi All,
>> Download the compressed stack "ResizeLivecodeGraphicsv01.livecode"
>> from this forum thread:
>> 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!
>> use-livecode mailing list
>> Please visit this url to subscribe, unsubscribe and manage your subscription
> use-livecode mailing list
> Please visit this url to subscribe, unsubscribe and manage your subscription
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription