imension 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 ?
>
>
>
se-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
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
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
> wrote:
>
>
> I can now get back to my "10-minute cleanup task" that I started 8 hours ago
> :-)
>
> Alex.
___
use-livecode mail
No, I don't, and that's probably what I should be doing.
I had not expected that changing the LEFT of a control would change both
X *and* Y coordinates of the enclosing group - but that is what seems to
happen; and that at least makes sense - any change to the control causes
an adjustment to b
Thanks, but no, I can't do that. lock messages will prevent the
"resizeControl" being fired for any sub-groups whose co-ordinates get
changed, so it would prevent proper layout for them. 'lock messages' is
good if you have all your controls directly re-positioned within your
resize handler - bu
Do you have the group size/position locked (lockLocation property)? If not,
moving a control could change the rect.
Thanks,
Brian
On May 3, 2020, 10:28 AM -0400, Håkan Liljegren via use-livecode
, wrote:
> You probably need to lock messages in the beginning of your resizeControl.
> Otherwise th
You probably need to lock messages in the beginning of your resizeControl.
Otherwise the group will adapt to your resizing of your controls. I usually
begin with both lock messages and lock screen, but the last is more for
optimization.
Håkan
On 3 May 2020, 16:22 +0200, Alex Tweedly via use-liv
I realized after the discussion last week about resizing that I was
missing the benefits of "resizeControl" being sent to each group, so I
changed one of my resize handlers to make use of groups (adding a few
groups along the way).
And it all went wrong :-(
Eventually I traced it down to the
