Re: Trying to understand the inner workings of ResizeStack

Filed a bug with a test stack. Bug 17133 Regards Terry ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription prefe

Re: Trying to understand the inner workings of ResizeStack

On Tuesday, March 15, 2016, Terence Heaford wrote: > > > On 15 Mar 2016, at 11:35, Trevor DeVore > wrote: > > > > This may have nothing to do with your code. El Capitan introduced some > > changes that LiveCode doesn't handle properly yet. The result is that you > > see your objects resizing on

Re: Trying to understand the inner workings of ResizeStack

> On 15 Mar 2016, at 11:35, Trevor DeVore wrote: > > This may have nothing to do with your code. El Capitan introduced some > changes that LiveCode doesn't handle properly yet. The result is that you > see your objects resizing on El Capitan (10.11) See this bug report: Not sure whether this is

Re: Trying to understand the inner workings of Resizestack

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

Re: Trying to understand the inner workings of ResizeStack

On Tue, Mar 15, 2016 at 5:15 AM, Terence Heaford wrote: > > I am using an iMac, El Capitan. > This may have nothing to do with your code. El Capitan introduced some changes that LiveCode doesn't handle properly yet. The result is that you see your objects resizing on El Capitan (10.11) See this

Re: Trying to understand the inner workings of ResizeStack

On 2016-03-15 10:15, Terence Heaford wrote: On 15 Mar 2016, at 09:03, Mark Waddingham wrote: 5. Is it necessary to call lock screen in myUpdateGeometry and dispatch “refreshChart”? No - the screen is implicitly locked before the resizeStack message is sent, and unlocked afterwards. Then the

Re: Trying to understand the inner workings of ResizeStack

> On 15 Mar 2016, at 09:03, Mark Waddingham wrote: > >> 5. Is it necessary to call lock screen in myUpdateGeometry and >> dispatch “refreshChart”? > > No - the screen is implicitly locked before the resizeStack message is sent, > and unlocked afterwards. Then the screen is explicitly updated.

Re: Trying to understand the inner workings of ResizeStack

On 2016-03-14 15:58, Terence Heaford wrote: 1. If you drag a window to resize it, the resize message is sent more than once? The OS dispatches a sequence of window resize requests, which the engine acts upon in turn. 2. and resizeStack is called each time? Is the screen locked more than onc

Re: Trying to understand the inner workings of Resizestack

On 2016-03-15 00:32, Paul Dupuis wrote: However, as of LiveCode 6.7.6, resizeControl is not sent to a disabled control when it's rectangle is changed. This is in keeping with messages not sent to disabled controls (like mouseDown, mosueUp, etc.) and yet it seems like a bug to me since whether

Re: Trying to understand the inner workings of Resizestack

I thought I would do put the milliseconds into tStart Put the milliseconds - tStart because I was thinking of going through and optimising all the script but had second thoughts when I saw the result. On dragging, to create the chart was only taking 4 to 5 milliseconds but when the group f

Re: Trying to understand the inner workings of Resizestack

On 3/14/2016 12:59 PM, Richard Gaskin wrote: > on resizeControl >refreshChart > end resizeControl > Just a caution for folks following this discussion of resizeStack, per Richard's suggestion, I've found the use of resizeControl to be a great way to modularize window geometry. However, as of

Re: Trying to understand the inner workings of Resizestack

I've not (yet) had to deal with particularly complex resize needs, so I've never run into the problem of not keeping up. But I've always had in the back of my mind the following idea (i.e. check it out, don't assume I know what I'm talking about :-) the system is going to throw a series of re

Re: Trying to understand the inner workings of Resizestack

On 03/14/2016 12:51 PM, Terence Heaford wrote: Have tried this as well. Bummer. Try blinking really fast. (sorry - I'm out of ideas) -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this

Re: Trying to understand the inner workings of Resizestack

I am using 6.7.9 but it happens in 7.1.2 and 8.0 (dp15). lockUpdates did not make any difference. Thanks Terry > On 14 Mar 2016, at 20:50, Scott Rossi wrote: > > If you're using LiveCode 7, the flashing may be an artifact that occurs > purely from redrawing/refreshing the screen. I've notice

Re: Trying to understand the inner workings of Resizestack

If you're using LiveCode 7, the flashing may be an artifact that occurs purely from redrawing/refreshing the screen. I've noticed this here, but don't have any reliable recipe that causes it. In any event, locking the screen and locking messages are the main steps to take, making sure to unlock a

Re: Trying to understand the inner workings of Resizestack

Have tried this as well. Thanks Terry > On 14 Mar 2016, at 19:48, Mark Wieder wrote: > > set the loc of this stack to -5000,-5000 ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage

Re: Trying to understand the inner workings of Resizestack

On 03/14/2016 12:43 PM, Terence Heaford wrote: set the topLeft of this stack to -5000,-5000 set the loc of this stack to -5000,-5000 -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visi

Re: Trying to understand the inner workings of Resizestack

Also just tried hide this stack and show this stack and the whole stack window flashes instead of just the group. Could we now be talking a bug? Thanks Terry > On 14 Mar 2016, at 19:43, Terence Heaford wrote: > > >> On 14 Mar 2016, at 19:17, Mark Wieder wrote: >> >> On 03/14/2016 12

Re: Trying to understand the inner workings of Resizestack

> On 14 Mar 2016, at 19:17, Mark Wieder wrote: > > On 03/14/2016 12:09 PM, Terence Heaford wrote: > >> I think perhaps I am asking to much of the engine as when resizeControl is >> received I don’t actually reposition/resize all the objects in the chart >> (90+), I actually delete the objects

Re: Trying to understand the inner workings of Resizestack

On 03/14/2016 12:09 PM, Terence Heaford wrote: I think perhaps I am asking to much of the engine as when resizeControl is received I don’t actually reposition/resize all the objects in the chart (90+), I actually delete the objects and recreate the chart. Ah. In that case, try locking the sc

Re: Trying to understand the inner workings of Resizestack

Interestingly, in OSX when you zoom full screen (which is a resize) it is as smooth as silk. I am not sure how this works but it is a shame we (OSX users) cannot have access to this mechanism from within resizeControl or resizeStack. No good for other but Mac users would probably love access to

Re: Trying to understand the inner workings of Resizestack

> On 14 Mar 2016, at 18:39, Richard Gaskin wrote: > > I think it may be subtler than that, but more easily fixed: > > When the contents of a group are resized, by default the group enclosing them > is resized to fit. > > So if you set the lockLoc of the group (and here I tend to set that for

Re: Trying to understand the inner workings of Resizestack

Terence Heaford wrote: >> On 14 Mar 2016, at 16:59, Richard Gaskin wrote: >> >> on resizeControl >> refreshChart >> end resizeControl > > Obviously, this works but does not cure the occasional flash that > occurs when reproducing the chart. > > I suspect perhaps the script along with all the re

Re: Trying to understand the inner workings of Resizestack

> On 14 Mar 2016, at 16:59, Richard Gaskin wrote: > > on resizeControl > refreshChart > end resizeControl Obviously, this works but does not cure the occasional flash that occurs when reproducing the chart. I suspect perhaps the script along with all the resizeControl messages is making it

RE: Trying to understand the inner workings of Resizestack

On March 14, 2016 10:56:32 AM "Ralph DiMola" wrote: 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. Sending a message in 0 puts it at the front of the queue but it still won't execute until th

Re: Trying to understand the inner workings of Resizestack

Ralph DiMola wrote: > 1) The resizestack message is sent once is live resizing if off. If > live resizing is on then a whole bunch of messages get stacked up > if you grab a corner and resize the stack. If you resizing code is > fast enough then resizing will look seamless, if your resizing takes

Re: Trying to understand the inner workings of Resizestack

Terence Heaford wrote: > 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? The simplest and most with-the-grain way to do it is

Re: Trying to understand the inner workings of Resizestack

riginal Message- > From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] 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

RE: Trying to understand the inner workings of Resizestack

e LiveCode Subject: Re: Trying to understand the inner workings of Resizestack > On 14 Mar 2016, at 15:29, Ralph DiMola 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 &g

Re: Trying to understand the inner workings of Resizestack

> On 14 Mar 2016, at 15:29, Ralph DiMola 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 g

RE: Trying to understand the inner workings of Resizestack

Heaford Sent: Monday, March 14, 2016 10:58 AM To: How to use LiveCode Subject: Trying to understand the inner workings of ResizeStack Resent message because of copy/paste from docs did not work well. Consider: on resizeStack pWidth,pHeight myUpdateGeometry dispatch "refresh

Trying to understand the inner workings of ResizeStack

Consider: on resizeStack pWidth,pHeight myUpdateGeometry dispatch "refreshChart" to group "netWorthChart" --pass resizeStack end resizeStack The docs say: The resizeStack message is sent after the resizing is finished. If the stack's liveResizing property is true,

Trying to understand the inner workings of ResizeStack

Resent message because of copy/paste from docs did not work well. Consider: on resizeStack pWidth,pHeight myUpdateGeometry dispatch "refreshChart" to group "netWorthChart" --pass resizeStack end resizeStack The docs say: The resizeStack message is sent after the resizing is