ResizeStack oddities
Posted: Wed Feb 02, 2022 5:27 pm
This post is based on another thread:
viewtopic.php?f=8&t=36710
The "resizeStack" message, as per the dictionary:
Nothing happens during the resize process. The breakpoint never catches anything. BUT, if one continually resizes for a little while, when the mouse is finally released, it can be seen in the message box literally dozens, if not more, random numbers being displayed in a stream. So the resizeStack message is sent repeatedly, but cannot be trapped at all. In that sense, the last part of the dictionary entry above is correct.
I think this is in fact better behavior than the dictionary states. That message ought to be sent continuously, similar to how the "mouseMove" message is sent. And it IS sent continuously, but one cannot see it at all, only getting proof at the very end.
Craig
viewtopic.php?f=8&t=36710
The "resizeStack" message, as per the dictionary:
In the stack script of a card:The resizeStack message is sent after the resizing is finished. This means that you cannot prevent a stack's size from being changed by trapping this message.
Code: Select all
on resizeStack
breakpoint
put random(99)
end resizeStack
I think this is in fact better behavior than the dictionary states. That message ought to be sent continuously, similar to how the "mouseMove" message is sent. And it IS sent continuously, but one cannot see it at all, only getting proof at the very end.
Craig