Group resizing.

[David Bovill]

Yes - this sort of bug is why having a couple of simple tools helps when developing these dynamically resizing widgets.
On 4 May 2020, 14:17 +0100, Alex Tweedly via use-livecode <use-livecode at lists.runrev.com>, wrote:
> David,
>
> thank you - that's a kind and generous offer to Zoom / pair on it.
> However, since the immediate problem is solved, I'd rather take a
> raincheck, and keep your offer in my back pocket for some future time I
> have a problem.
>
> Summary of this case - when you do resizing based on groups, you should
> be sure to have the lockLocation of the groups set true.
>
> I had a silly typo
>    set the top of something to the bottom of another+10
> and I had
>    set the top of something to the bottom of another+1000
>
> If lockLocation had been set, that would have been trivially obvious,
> and fixed in 30 seconds. However, it wasn't, so the group grew out of
> scale and obscured  most of the window, including where the problematic
> controls should have been - so I couldn't see they had gone astray..
>
> And by bad luck, when I started adding "put .... to msg" statements, I
> happened to span a bit of code that *only* tried to change X
> coordinates, and was actually changing Y coords (because of group
> inclusion). So I spent a long time down a rabbit hole of trying to see
> find which code could be doing that, not realizing this "feature" that
> changing one dimension would expand both dimensions of the group.
>
> Thanks again,
>
> Alex.
>
> P.S. any thoughts on another group Zoom for Livecoders ? Haven't heard
> more from Heather (and they may be busy), so maybe we should try to
> arrange a community get-together ?
>
>
> On 04/05/2020 10:09, David Bovill via use-livecode wrote:
> > Trying to understand this thread. I’ve been doing nested group resizing for all my work now for several years - it has been difficult often to debug track errors because of all the nested messages.
> >
> > As a result I’ve had to make a bunch of tools to test each nested element before they are combined, and also I’ve developed a consistent style of doing it - which may mean that I’m not coming across the issue you report.
> >
> > My suggestion Alex is the only way to explore this is to jump into a Zoom where we can share practice and see visually the issue? It would also be more fun at this time if lock down?
> >
> > Feel free to pick a time if that appeals - I got nothing better to do :)
> >
> > • https://woven.com/c/david62/pairprogramming
> >
> > On 4 May 2020, 01:38 +0100, scott--- via use-livecode <use-livecode at lists.runrev.com>, wrote:
> > > Oh good, I was hoping I wasn’t the only one.
> > >
> > > —
> > > Scott
> > >
> > >
> > > > On May 3, 2020, at 11:28 AM, Alex Tweedly via use-livecode <use-livecode at lists.runrev.com> wrote:
> > > >
> > > > <snip>
> > > > I can now get back to my "10-minute cleanup task" that I started 8 hours ago :-)
> > > >
> > > > Alex.
> > >
> > > _______________________________________________
> > > use-livecode mailing list
> > > use-livecode at 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 at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode