Nudge painfully slow

[dunbarx]

Another issue with the moving of controls in my attempt to love v.8.

LC v.8.1.6

If I have more than a dozen or so controls, select them all and then nudge with the arrowKeys, the action is so slow I initially thought LC had frozen, and had to force quit the app. It turns out that if I select 100 controls and nudge a few times, I can go out to lunch and when I come back the action will have finally completed.

This is in line with two other threads in this pane, and there is a chance that increasing RAM may be the answer to all of them. I have 8G installed in a 27" iMac, and am going to increase that to 24G. If that is the only issue, then well and good. If not, you will all hear about it.

Craig Newman

[jmburnod]

Hi Craig,
After your last post about LC 8
I'm almost happy to tell you I have the same issue
Jean-Marc

[FourthWorld]

Is the Project Browser open which nudging? I find it a bit zealous with its updates.

If not, I wonder if "lock screen" and "lock messages" may be missing from the IDE handler managing that.

[dunbarx]

No project browser. Just molasses.

Craig

[FourthWorld]

If you can make a simple test stack that runs faster you can submit a bug report against the IDE. And if it doesn't run faster you can submit a report against the engine. Either way, you'll either get a fix or a good understanding of what changed. But hopefully a fix.

[dunbarx]

If you can make a simple test stack that runs faster you can submit a bug report against the IDE. And if it doesn't run faster you can submit a report against the engine

Richard.

I can make a stack that runs faster if I only select a handful of controls. Is that what you meant? Even I would not begrudge LC for a slowdown as the number of selected controls gets large. It is just that I do not think a dozen can be considered "large".

I will complain and see what they say.

Craig

[dunbarx]

There was an earlier report that noted these issues go away when the PI is not open.

It is all true. I submitted a similar complaint.

Craig

[FourthWorld]

There was an earlier report that noted these issues go away when the PI is not open.

It is all true. I submitted a similar complaint.

BZ# so we can follow the discussion?

[dunbarx]

Bug # 20672

Craig

[dunbarx]

Installed 24G of RAM. Nudge problem did not go away.

As I write this, I have about 150 controls "in nudge mode", upon six clicks of an arrowKey. The first one happened right away. Ah. I just saw one step occur. I am timing the whole thing...

OK. About four minutes. All the controls released, and I can go back to work. Charles Babbage would have thought this intolerable.

Craig

[bogs]

Installed 24G of RAM. Nudge problem did not go away.

No halfway measures now, eh
Just of a curiosity, and I hope I phrase this so as not to offer offense. View it in the nature of a subjective test.

I created new mainstacks in vers. 6.x - 7.x I dragged a button on, replicated it 100x, and then 'nudged', using the arrow keys, and the property inspector. no problems, although it was a tad disjointed when using the prop. inspector in 7.x (but not slow)

I then made a stack in 8.1.6, dragged the button and..... no replicate? Huh, I never made the connection, or at least, was unable to find it (something I use a LOT). ok, back to 7.x made stack rep'd a 100 buttons etc.
...Opened that stack in 8
...Nudge in the prop. inspector, well, forget it. Much as what Craig is experiencing.
...Nudging with the arrow keys on the keyboard, as before, no so bad. My guess would be something in the prop. inspector really aint cutting it.

Something for you to try, I guess Craig. I hope it helps

[jacque]

The IDE would ideally lock the screen before each move and unlock it after. Screen redraws are expensive. It doesn't sound like it's doing that, but you could write your own handler I suppose. Another workaround might be to group the objects and move the whole group.

[bogs]

The IDE would ideally lock the screen before each move and unlock it after. Screen redraws are expensive.

I'm not sure I follow, so check me on this. If your moving the objects with the arrow keys on the keyboard, which works fine and quickly (least here), then wouldn't it indicate something other than a lock screen issue? After all, the controls moving are what I would think require the redraw, not the control making the move (keyboard vs. nudge button in the prop. inspector).

Am I way off?

Btw Craig, I increased the count of buttons to 808 and then again moved them with the arrow keys on the keyboard. It is tons smoother, if you have to move large amounts of controls, I'd sure suggest it. Or Jacque's group method. Or handler.

[dunbarx]

Or close the PI.

That is the culprit, at least here. And maybe OS 10.9

Craig

[bogs]

LOL, I was actually unable to test using the keyboards arrow keys with the PI open, since unlike every single version before 8.x, the focus won't shift from the PI to the stack! Talk about a DOH!