Trying to understand the inner workings of Resizestack

[Paul Dupuis]

On 3/15/2016 4:51 AM, Mark Waddingham wrote:
> Anyway, I couldn't find any report of this in the quality center so I
> filed it here: http://quality.livecode.com/show_bug.cgi?id=17123
>
> Warmest Regards,
>
> Mark. 

Mark,

Thank you for adding the bug. I have been aware of this "bug" for some
time, but never seemed to make the time to log it, which is bad of me. I
hate it when people find bugs in our product and never report them, so I
should make sure I do better at "upstream" reporting.

"resizeControl" not being received by disable controls is one of those
things I think folks that used it just discover and work-around. As in
most cases the resizing is being caused by a primary resizeStack
handler, in the resizeStack handler you can just add:

if the disabled of control x is true then
  send "resizeControl" to control x
end if

This, of course, causes the control to execute it's resizeControl
handler explicitly.

Still, it is best if you can use the engine native message management to
let changes happen, so thank you again for logging this bug.