iOS Simulator Behaves Strangely in LC8DP15

We are kicking off development of a new app. I developing this from ground zero in LC8 (dp 15) LC --> Preferences --> Mobile Support --> iOS SDKs # giving me a green light Available device SDKs: 9.2 Available simulators: 9.2 Stack is set to fullscreenMode showAll But when I run it in the

free book

Richard kindly posted this link in Facebook: https://www.packtpub.com/packt/offers/free-learning It’s a free copy of the first edition of the book I wrote. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe,

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-Render Card-image that has moved on disk

I think it's imageCacheLimit On March 12, 2016 at 5:03:13 PM, Monte Goulding (mo...@appisle.net) wrote: There has been an image cache for a while. You can clear it by setting the imageCacheSize (I think that's the name of the property) to 0 then back to whatever it

Modularity

A while back there was some talk about making it possible that when one wanted to export standalones from Livecode one could choose what capabilities to include and which to exclude. Recently "elsewhere" a chap working with Livecode was complaining about the 'bloat' in a standalone between

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

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

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

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

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

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

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

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

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

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: 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

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

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

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

Re: Trying to understand the inner workings of Resizestack

I have tried send in 0 seconds and read the docs. Using in 0 seconds seems to just delay the send call until all resizeStack messages have been completed. It does not allow the resizing of the chart dynamically as the size of the window is resized only on completion of the resizing process.

RE: Trying to understand the inner workings of Resizestack

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.

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

RE: Trying to understand the inner workings of Resizestack

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 too long the it will be

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

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

$_SESSION not working on LiveCode Server 7.1.3-rc-1

Just a quick note to anyone who might be experiencing weirdness in their .lc scripts ... it's not you it's LiveCode 7 not managing $_SESSION properly http://quality.livecode.com/show_bug.cgi?id=14452 - "The first 90% of the task takes 90% of the time, and the last 10% takes the other 90%

Re: [ANN] tmControl2 v2.2 Released for LiveCode 7

A few people have asked for specifics about the controls included in the tmControl2 package. I've updated the product page with a visual list of the controls: http://tmtools.tactilemedia.com/tmcontrol2/ Hope this helps. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On