I went through this a while back(3 years or so). If I recall J. Landman Gay
helped me on this.
I believe(someone correct me if I'm wrong) if you do a "send in 0 seconds" It
will in effect do call and return control to the resizestack handler. If I'm
correct then this method would work for you.
I just moved all my resizing code to the stack and made the problem go away. I
have one routine for each card that is named for each
card(resize_card1name,resize_card2name)and a master routine that is called from
the resizestack message that does a "do ("resize_"&the short name of this card)"
Ralph DiMola
IT Director
Evergreen Information Services
[email protected]
-----Original Message-----
From: use-livecode [mailto:[email protected]] On Behalf Of
Terence Heaford
Sent: Monday, March 14, 2016 11:40 AM
To: How to use LiveCode
Subject: Re: Trying to understand the inner workings of Resizestack
> On 14 Mar 2016, at 15:29, Ralph DiMola <[email protected]> wrote:
>
> 3) I would not do any dispatching or sending in time in a resizestack
> handler. This is probably the source of your flashing. Get the work done and
> then pass the resizestack message to the engine. I found out that sometimes
> things can go sideways if you don’t pass the resizestack message.
Sorry, I don’t quite understand what you are saying.
I am using the resizeStack message to know that the window has changed size,
then I call a routine that redraws a chart. I need to send or dispatch to the
group that will contain the chart.
How else can I do it?
Thanks
Terry
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
