LiveCode Forums.

This started with another thread in this pane:
http://forums.livecode.com/viewtopic.php?f=9&t=34623

I made a test stack, one button and two fields, with this in the button script: I got the beachBall, and the Mac dialog "Force Quit Applications" showed LiveCode "not responding". We have all seen that sort of thing. I force-quit LC, thinking it had hung.

So I knocked the repeat value down to 10,000, got a mere flash of a beachBall and then 100,000 chars were loaded into the field. So I increased the repeat value in steps, and, though the beachBall lasted longer, I got a repeat value of 50,000 (500,000 chars) to load successfully. It took a couple of minutes though, and the "Not Responding" was in the dialog the whole time. That cleared when the process finally completed. But someone would have thought that the process has failed, when in fact my machine and LC were just not talking to each other.

They eventually made up.

I then re-tried 100,000 for a repeat value (1,000,000 chars), and that took 14 minutes. Larger repeat values require longer than linear times, so I am stopping at the one million character test. I suspect that time notwithstanding, there may be no such limit.

But if I learned anything, it was that an app like LC that is "not responding" may in fact just be very busy, and the machine is misinterpreting that to mean it has gone off into the weeds. It may have, of course, but it seems to have always been able to find its way back.

On another note, I have a card with a field that already contains 1,760.000 chars. It takes LC about seven seconds, with the beachBall showing up for the occasion, to display that card.

Craig

The "not responding" issue is typical on Windows when a tight repeat loop hogs all the cycles. This is why I frequently mention including a line inside the loop I had heard this was originally "a Mac thing" that got resolved. But it has always been "a thing" on Windows, and still is.

Sparkout.

I will try this and see if it prevents the appearance of the "not responding" gizmo.

Craig

dunbarx wrote: ↑

Thu Sep 10, 2020 9:39 pm

This started with another thread in this pane:
http://forums.livecode.com/viewtopic.php?f=9&t=34623

I made a test stack, one button and two fields, with this in the button script:

Code: Select all

on mouseUp
   put the seconds into tStart
   put "1234567890" into temp -- ten chars
   repeat 100000 -- a 1,000,000 char test
      put temp after accum
   end repeat
  
   put accum into fld 1
   put the seconds -tStart into fld 2
end mouseUp

I got the beachBall, and the Mac dialog "Force Quit Applications" showed LiveCode "not responding". We have all seen that sort of thing. I force-quit LC, thinking it had hung.

Craig,

what you are testing is the limit of the length of a line in Livecode. I am surprised it did not crash. I think it is 64000 something and the formattedWidth is about half of it. See user guide. Your code produces one line.

Try adding a return after each 10 chars = temp
those 1.1 million chars (including returns) take about 1 second

Kind regards
Bernd

Natural language, or anything with white space, is a much better test to run than a long 10MB string with no spaces or returns.

LC has a known issue attempting to render a string > ~64k (which in the real world is seldom exceeded) with no white space, and the internal routines to attempt line-wrapping are, I'm told, not trivial.

So at a minimum you'll want to have a reasonable amount of spaces in that test data.

And if you're looking at load performance independent of line-wrap rendering, make sure the data has enough CRs in it and then set the field's dontWrap to true.

Bernd.

There is indeed a published limit to the number of chars in one line in a field: 64K.

But I loaded many more into one line, even with my smallest repeat value. That limit seems not to be valid.

Craig

Try sorting with that.

The internal structure will let you do some things with longer lines, but not others.

Richard.

I get all this, and do not want to promote too much esoterica. Its late.

Except for this, how would one sort the chars of a field without fooling around with the string?

Craig

dunbarx wrote: ↑

Fri Sep 11, 2020 4:29 am

Richard.

I get all this, and do not want to promote too much esoterica. Its late.

Except for this, how would one sort the chars of a field without fooling around with the string?

It must be late, as I don't understand the question. The point of sorting is exactly to fool around with the string.

Let's get some rest and I'll read your reply with a fresh cup of coffee in the morning.

Richard.

Its early. Just as bad

I was, er, fooling around with the string, in that one cannot sort the characters of a string. I have had to do this in the past, and have had to: I often wondered why the "sort container" command did not allow characters to be sorted directly.

Craig

I'm not exactly sure what that last code block should do, but in the original just use "123456789 " instead of "1234567890" in your temp var and you'll have lots of spaces reasonably matching what one would expect to find in real-world text.

Richard.

If you have spaces, you have a "delimiter" with which to sort. My original fooling around had none. The line: was pseudoCode, er, very, very pseudo like the other two. I meant something like: Because there is no "sort chars" in LC.

Craig