Re: Move command on iOS

I did leave the group set to dynamic, actually. When I'm done tinkering with rotation adjustments I'll see if that helps. Thanks. On 8/4/18 4:06 PM, Randy Hengst via use-livecode wrote: Did you leave the controls on dynamic? I found leaving them at static helped. be well, randy

Re: Move command on iOS

On 8/4/18 5:11 PM, Monte Goulding via use-livecode wrote: So I guess ensuring it is positioned correctly for the device before the first move and the hide move hides the whole thing would be a good place to start. I saw that, just fixed it today. This stack was made 6 years ago before we had

Re: Move command on iOS

> On 5 Aug 2018, at 5:00 am, J. Landman Gay via use-livecode > wrote: > > I don't quite know why my stack ran okay on Monte's phone, and my > stripped-down test with the same code ran okay in the simulator, but my real > stack failed. Weird. When I said it worked ok here I should have

Re: Move command on iOS

Did you leave the controls on dynamic? I found leaving them at static helped. be well, randy www.classroomFocusedSoftware.com > On Aug 4, 2018, at 3:00 PM, J. Landman Gay via use-livecode > wrote: > > I did tinker with accleratedRendering when the problem first appeared. I > turned it off

Re: Move command on iOS

I did tinker with accleratedRendering when the problem first appeared. I turned it off before the move command and back on afterward, but it didn't help. I also changed the time so that the move was slower, but that didn't work either. Panos seems to have identified the reason for the failure

Re: Move command on iOS

Sorry I’m a bit late to this strand, but yes, I’ve seen what you’re describing Jacque. I’ve seen it in the simulator and when loaded on the iPad. Have you tried turning off acceleratedRendering and setting to static? As I shared earlier with the list, the problem I’m seeing includes slowdowns

Re: Move command on iOS

Hello all, I have added a comment to the bug report. Best, Panos -- On Sat, Aug 4, 2018 at 7:53 AM, Monte Goulding via use-livecode < use-livecode@lists.runrev.com> wrote: > This seems to work fine here testing on a device > > > On 4 Aug 2018, at 2:20 pm, J. Landman Gay via use-livecode < >

Re: Move command on iOS

This seems to work fine here testing on a device > On 4 Aug 2018, at 2:20 pm, J. Landman Gay via use-livecode > wrote: > > I jumped the gun and sent a download link to both of you. But you're hours > ahead of him so you have time to intercept. :) > > On 8/3/18 10:25 PM, Monte Goulding via

Re: Move command on iOS

I jumped the gun and sent a download link to both of you. But you're hours ahead of him so you have time to intercept. :) On 8/3/18 10:25 PM, Monte Goulding via use-livecode wrote: Hmm… feel free to send through to me as I’m intrigued. I will send the stack to Panos if I can’t figure out what

Re: Move command on iOS

Hmm… feel free to send through to me as I’m intrigued. I will send the stack to Panos if I can’t figure out what is going on so he can put it wherever private test stacks go. > On 4 Aug 2018, at 1:05 pm, J. Landman Gay via use-livecode > wrote: > > Skip the test, it works fine in isolation.

Re: Move command on iOS

Skip the test, it works fine in isolation. Bug report is here: https://quality.livecode.com/show_bug.cgi?id=21461 But there must be something else going on so I should send the real stack to either you or Panos I guess. On 8/3/18 9:27 PM, J. Landman Gay via use-livecode wrote: Here's the

Re: Move command on iOS

Here's the relevant part of the script. There's only one "move" command: put the long id of grp "iOSPicker" into tGrp get the height of tGrp div 2 put the height of this cd - it into tDestV show tGrp -- before updating text wait 1 millisecond with messages move tGrp to

Re: Move command on iOS

I'm not using visual effects so it probably isn't that bug. I'll put in a report when I can get a test stack together. The simulator I'm using is set up for 11.4 so the problem is in at least iOS 11 and 12 both. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software |

Re: Move command on iOS

@Jacque I’ve had a look around the engine… would be interested to know if you are moving without waiting or not (if that makes a difference). It looks like the most likely cause of what you are seeing is multiple calls to `move` the object to a location. The second of which will look like the

Re: Move command on iOS

@Jacque there was this one also but that is visual effects only https://quality.livecode.com/show_bug.cgi?id=21434 > On 4 Aug 2018, at 10:18 am, Monte Goulding via use-livecode > wrote: > > Hmm… I patched the crash at startup when not in

Re: Move command on iOS

Hmm… I patched the crash at startup when not in acceleratedRendering mode for iOS 12. I don’t think it will have much to do with the move command in acceleratedRendering mode. I did recently fix something in acceleratedRendering mode in a stack that had a group coming in from the side that was

Re: Move command on iOS

Are you testing in iOS 12? This is the exact problem I’m having (that Monte just patched today). Sounds like it should be fixed in 9.0.1.rc2 --Andrew Bell --Sent from my iPhone >>> > From: "J. Landman Gay" > To: LiveCode Mailing List > Subject: Move command on iOS > Message-ID: >