Re: Maximum field size
Actually, that wasn't me, it was someone else. I can't swim. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On January 20, 2023 1:43:39 PM Richard Gaskin via use-livecode wrote: As for field limits, I believe Jacque summarized them well: - Per line: 64k chars per line when rendered without text wrap (rendering limit only; field text still addressable, and everything works swimmingly in a var) ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
David Epstein wrote: > Richard Gaskin asks “Why?” > > I have developed a set of routines to analyze tabular data. For KB > or MB-sized files, it is convenient to display them in a field. It > would be simplest if I could also load GB-sized files and use my > routines unchanged, but I accept that this is impractical. But in > order to design workarounds I’d like to get as much clarity as > possible on what limits I am working around. Do you read the text when it's measured in megabytes? R and other data processing tools encourage habits of displaying results, but rarely the data set as a whole. Of course I haven't seen what you're working on, and I've had my own moments now and then when just randomly scanning large data sets has yielded "a ha!" insights, so I can appreciate the desire for your work with Cornell. One option to consider, if practical for your needs, is that a one-time change to work with the data in a variable for all data regardless of size would at least obviate the need for special-casing data sets of specific size. As for field limits, I believe Jacque summarized them well: - Per line: 64k chars per line when rendered without text wrap (rendering limit only; field text still addressable, and everything works swimmingly in a var) - Total - Logical: 4GB (32-bit ints used for allocation) - Total - Practical: a mix of: available addressable space on the current system in its current state, likely at times requiring much more than the size of the data on disk given the iterative allocation calls to move the I/O buffer into the variable space, mitigated by any limitations imposed by the host OS's allocation routines provided for contiguous blocks (Mark Waddingham has cited in this many times how Win32 APIs have some limits on contiguous allocation far below the logical 4GB threshold). - Total - Anecdotal: I use the Gutenberg KJV Bible file frequently for stress testing text routines, but while we think of the Bible as a large text it weighs in at just 4.5 MB. In rarer cases where I've needed to probe for outliers I've created test sets above 100 MB without issue, but begin to see major slowdowns long before that is line-wrapping calculations are needed, and further above ~100 MB significant slowdowns for display, scrolling, and save operations. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
I was going to suggest polyGrid. I used it when it was still in development to solve the text overrun problem. It works like the datagrid, only loading the visible text in batches as you scroll and performs very well. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On January 20, 2023 9:25:23 AM David Epstein via use-livecode wrote: My testing attempts, like Bernd’s, show that the important “limits” are not just what LC can display in a field but what it can display without making things too slow. I am also wondering if the new polyGrid has different characteristics, either its absolute limits or its performance when heavily populated. Richard Gaskin asks “Why?” I have developed a set of routines to analyze tabular data. For KB or MB-sized files, it is convenient to display them in a field. It would be simplest if I could also load GB-sized files and use my routines unchanged, but I accept that this is impractical. But in order to design workarounds I’d like to get as much clarity as possible on what limits I am working around. David Epstein ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
My testing attempts, like Bernd’s, show that the important “limits” are not just what LC can display in a field but what it can display without making things too slow. I am also wondering if the new polyGrid has different characteristics, either its absolute limits or its performance when heavily populated. Richard Gaskin asks “Why?” I have developed a set of routines to analyze tabular data. For KB or MB-sized files, it is convenient to display them in a field. It would be simplest if I could also load GB-sized files and use my routines unchanged, but I accept that this is impractical. But in order to design workarounds I’d like to get as much clarity as possible on what limits I am working around. David Epstein ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
... ok. But first, can you provide an example of ANY application that displays that much text or that many lines in a field? A-Whaaay back when, Microsoft ran into this problem with large Word and Excel files. They got around it by developing a paging system that only kept in memory a certain number of pages before and after the currently displayed page. If it is absolutely necessary for this app to display that much data, I suggest developing a paging engine that tracks the vScroll to determine what to display and cache. (caching just for speed.) Re-engineering the field object is not the solution methinks. It would probably negatively impact the performance of the field object. FWIW the Datagrid Library ALSO has paging built in. Bob S On Jan 19, 2023, at 12:16 , Paul Dupuis via use-livecode mailto:use-livecode@lists.runrev.com>> wrote: All the responses about crashing - because lines are too long (exceeding 65K chars or 32K x in line length) or there are too many lines (and so 32,767px of scrollable height is not enough) - strongly indicated that an overhaul of the standard field object is needed in LC 10, or, more likely, in LC11. No matter what a developer or user tries to do with a field, it should not crash. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
I tried to put text into a field on an arm MacBook Pro 32 GB memory, LC 9.6.9 rc2 running natively. I realise that this is 64 bit. I took a couple of lines of Lorem Ipsum and put it into a field. Then I put the formattedText of that field into the field to force lineFeeds at every visible line. 35 lines overall. I then put that text a million times into a variable. That variable was put into a field that was a little wider than the originating field to avoid line wrapping in the target field and also set the dontWrap of the target field to true. The result: 35.000.000 Lines in the field 1.109.000.000 bytes, roughly 1.1 GigaBytes in the field 525.000.000 Pixel line 1 to -1 formattedHeight 160 seconds to fill field App Memory Size went up to 17 GB, went down to 480 Mb after clearing the field. The field could be scrolled although with a lot of Pizza spinning. After some fiddling with scrolling down to the end I was able to insert a return after the last line. (a bit of pizza) Blinking cursor in field very slow. LC slowed down but responded reasonably once the focus was away from the long field. LC did not crash but did not really like that much text in a field. Kind regards Bernd ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
All the responses about crashing - because lines are too long (exceeding 65K chars or 32K x in line length) or there are too many lines (and so 32,767px of scrollable height is not enough) - strongly indicated that an overhaul of the standard field object is needed in LC 10, or, more likely, in LC11. No matter what a developer or user tries to do with a field, it should not crash. When you put your application in customer hands, you have no idea what they may do. Our application lets researchers open and analyze text documents. In the context of that analysis, documents more than a few hundred pages long seemed unlikely to be something that would ever occur. And even then, those seemed rare. Then a customer contacted us working on a document that was 1000s - nearly 10,000 pages in length! It didn't make sense to me, but it dd to them. Now I dread the day when someone tries a document that is hundreds of thousands of pages (or many 10s of thousands or some kind of data set that is an equivalent) and our app crashed because field limits where exceeded. No error code we can trap for, just boom and done. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
RE: Maximum field size
Craig, You are probably exceeding the 32k pixel limit of the field height. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Craig Newman via use-livecode Sent: Thursday, January 19, 2023 2:00 PM To: How to use LiveCode Cc: Craig Newman Subject: Re: Maximum field size Guys, (and Jacque) I made my test with lines of 14 chars. Lots of lines. LC crashes. Craig > On Jan 19, 2023, at 10:10 AM, Craig Newman wrote: > > The stack I made to test this became corrupted after a couple of runs. I > guess the way to do this is to increase the length until a crash, not > decrease. > >> On Jan 19, 2023, at 10:09 AM, Craig Newman >> wrote: >> >> But I assume that there is a value where a field can be loaded and display a >> large amount of text. It would be simple to find that value if LC didn’t >> crash each time it was attempted along the way. >> >> Craig >> >>> On Jan 19, 2023, at 10:06 AM, Craig Newman >>> wrote: >>> >>> David. >>> >>> You want to display 1.39 GB in a field? Will it scroll? >>> >>> I made a quick test stack that created a variable with a length of 1.4 GB. >>> No problem. >>> >>> But when I tried to put that variable into a field, LC crashed. When I >>> tried to put 140 MB into a field, same crash. I did not continue to reduce >>> the length of that variable until the field could be loaded. >>> >>> Craig >>> >>>> On Jan 18, 2023, at 7:46 PM, Paul Dupuis via use-livecode >>>> wrote: >>>> >>>> I thought the theoretical limit was 4GB (32bits of characters) but I may >>>> be wrong or there may be practical limits below that threshold. >>>> >>>> >>>> On 1/18/2023 7:29 PM, David Epstein via use-livecode wrote: >>>>> How many rows or columns or characters can reasonably be displayed in a >>>>> LiveCode field? A 1.39 GB text file seems pretty clearly to surpass the >>>>> limit, but how much do I need to subdivide it? >>>>> >>>>> David Epstein >>>>> ___ >>>>> use-livecode mailing list >>>>> use-livecode@lists.runrev.com >>>>> Please visit this url to subscribe, unsubscribe and manage your >>>>> subscription preferences: >>>>> http://lists.runrev.com/mailman/listinfo/use-livecode >>>> >>>> >>>> ___ >>>> use-livecode mailing list >>>> use-livecode@lists.runrev.com >>>> Please visit this url to subscribe, unsubscribe and manage your >>>> subscription preferences: >>>> http://lists.runrev.com/mailman/listinfo/use-livecode >>> >> > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
Richard. As I mentioned, I wanted to make sure the field had scroll capabilities. ;-) > On Jan 19, 2023, at 12:54 PM, Richard Gaskin via use-livecode > wrote: > > David Epstein wrote: > > > How many rows or columns or characters can reasonably be displayed > > in a LiveCode field? A 1.39 GB text file seems pretty clearly to > > surpass the limit, but how much do I need to subdivide it? > > Jacque noted the machine limits, but I'm curious about a human question: > > At an average of ~3,000 characters per printed page, if I'm doing the math > right then 1.3 GB of text = 433,333 pages worth of content. > > For comparison, the entire text of the KJV Bible from the Gutenberg Project > is 4.5 MB. > > What are you displaying for the user to read during the session? > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > > ambassa...@fourthworld.comhttp://www.FourthWorld.com > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
Guys, (and Jacque) I made my test with lines of 14 chars. Lots of lines. LC crashes. Craig > On Jan 19, 2023, at 10:10 AM, Craig Newman wrote: > > The stack I made to test this became corrupted after a couple of runs. I > guess the way to do this is to increase the length until a crash, not > decrease. > >> On Jan 19, 2023, at 10:09 AM, Craig Newman >> wrote: >> >> But I assume that there is a value where a field can be loaded and display a >> large amount of text. It would be simple to find that value if LC didn’t >> crash each time it was attempted along the way. >> >> Craig >> >>> On Jan 19, 2023, at 10:06 AM, Craig Newman >>> wrote: >>> >>> David. >>> >>> You want to display 1.39 GB in a field? Will it scroll? >>> >>> I made a quick test stack that created a variable with a length of 1.4 GB. >>> No problem. >>> >>> But when I tried to put that variable into a field, LC crashed. When I >>> tried to put 140 MB into a field, same crash. I did not continue to reduce >>> the length of that variable until the field could be loaded. >>> >>> Craig >>> On Jan 18, 2023, at 7:46 PM, Paul Dupuis via use-livecode wrote: I thought the theoretical limit was 4GB (32bits of characters) but I may be wrong or there may be practical limits below that threshold. On 1/18/2023 7:29 PM, David Epstein via use-livecode wrote: > How many rows or columns or characters can reasonably be displayed in a > LiveCode field? A 1.39 GB text file seems pretty clearly to surpass the > limit, but how much do I need to subdivide it? > > David Epstein > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode >>> >> > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
David Epstein wrote: > How many rows or columns or characters can reasonably be displayed > in a LiveCode field? A 1.39 GB text file seems pretty clearly to > surpass the limit, but how much do I need to subdivide it? Jacque noted the machine limits, but I'm curious about a human question: At an average of ~3,000 characters per printed page, if I'm doing the math right then 1.3 GB of text = 433,333 pages worth of content. For comparison, the entire text of the KJV Bible from the Gutenberg Project is 4.5 MB. What are you displaying for the user to read during the session? -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
The theoretical field text limit is about 4 GB but the practical limit depends on available RAM. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On January 19, 2023 9:12:31 AM Craig Newman via use-livecode wrote: The stack I made to test this became corrupted after a couple of runs. I guess the way to do this is to increase the length until a crash, not decrease. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
On 1/19/23 07:26, Niggemann, Bernd via use-livecode wrote: From the User Guide: Maximum length of a line in a field: 65,536 characters storage No more than 32,786 pixels wide for display If you put lines longer above limits then LC will hang/crash The amount of lines a field can hold is a lot higher provided the individual lines are not too long. That's good to know, but crashing doesn't seem like a good way to enforce those limits. -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
Thanks to Bernd for this: > Maximum length of a line in a field: > 65,536 characters storage > No more than 32,786 pixels wide for display This seems to mean we can have a 65k long line only if each character’s width is around half a pixel. And that if the character width is 10 pixels the maximum line is 6,553 characters. Or does “for display” mean something else? And, if we respect the line length limit, is the number of lines in a field limited only by however much of minimum(RAM, LC’s 4GB “total addressable space”) is not being used by something else? So for example would trying to load a 2.1 GB variable in a field surpass the 4GB limit, because the variable and the field would each need 2.1 GB? Best wishes, David Epstein ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
>> But when I tried to put that variable into a field, LC crashed. When I tried >> to put 140 MB into a field, same crash. I did not continue to reduce the >> length of that variable until the field could be loaded. Craig, >From the User Guide: Maximum length of a line in a field: 65,536 characters storage No more than 32,786 pixels wide for display If you put lines longer above limits then LC will hang/crash The amount of lines a field can hold is a lot higher provided the individual lines are not too long. Kind regards Bernd ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
RE: Maximum field size
David, I believe the field limit for X and Y is 32767 pixels. Or is it 65535? 32767 sticks in my head. I have run into this limit a few times and had to chunk the data in/out the field as the user scrolls. As Craig noted variables don't have this limit. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Craig Newman via use-livecode Sent: Thursday, January 19, 2023 10:07 AM To: How to use LiveCode Cc: Craig Newman Subject: Re: Maximum field size David. You want to display 1.39 GB in a field? Will it scroll? I made a quick test stack that created a variable with a length of 1.4 GB. No problem. But when I tried to put that variable into a field, LC crashed. When I tried to put 140 MB into a field, same crash. I did not continue to reduce the length of that variable until the field could be loaded. Craig > On Jan 18, 2023, at 7:46 PM, Paul Dupuis via use-livecode wrote: > > I thought the theoretical limit was 4GB (32bits of characters) but I may be wrong or there may be practical limits below that threshold. > > > On 1/18/2023 7:29 PM, David Epstein via use-livecode wrote: >> How many rows or columns or characters can reasonably be displayed in a LiveCode field? A 1.39 GB text file seems pretty clearly to surpass the limit, but how much do I need to subdivide it? >> >> David Epstein >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
The stack I made to test this became corrupted after a couple of runs. I guess the way to do this is to increase the length until a crash, not decrease. > On Jan 19, 2023, at 10:09 AM, Craig Newman wrote: > > But I assume that there is a value where a field can be loaded and display a > large amount of text. It would be simple to find that value if LC didn’t > crash each time it was attempted along the way. > > Craig > >> On Jan 19, 2023, at 10:06 AM, Craig Newman >> wrote: >> >> David. >> >> You want to display 1.39 GB in a field? Will it scroll? >> >> I made a quick test stack that created a variable with a length of 1.4 GB. >> No problem. >> >> But when I tried to put that variable into a field, LC crashed. When I tried >> to put 140 MB into a field, same crash. I did not continue to reduce the >> length of that variable until the field could be loaded. >> >> Craig >> >>> On Jan 18, 2023, at 7:46 PM, Paul Dupuis via use-livecode >>> wrote: >>> >>> I thought the theoretical limit was 4GB (32bits of characters) but I may be >>> wrong or there may be practical limits below that threshold. >>> >>> >>> On 1/18/2023 7:29 PM, David Epstein via use-livecode wrote: How many rows or columns or characters can reasonably be displayed in a LiveCode field? A 1.39 GB text file seems pretty clearly to surpass the limit, but how much do I need to subdivide it? David Epstein ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode >>> >>> >>> ___ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
But I assume that there is a value where a field can be loaded and display a large amount of text. It would be simple to find that value if LC didn’t crash each time it was attempted along the way. Craig > On Jan 19, 2023, at 10:06 AM, Craig Newman wrote: > > David. > > You want to display 1.39 GB in a field? Will it scroll? > > I made a quick test stack that created a variable with a length of 1.4 GB. No > problem. > > But when I tried to put that variable into a field, LC crashed. When I tried > to put 140 MB into a field, same crash. I did not continue to reduce the > length of that variable until the field could be loaded. > > Craig > >> On Jan 18, 2023, at 7:46 PM, Paul Dupuis via use-livecode >> wrote: >> >> I thought the theoretical limit was 4GB (32bits of characters) but I may be >> wrong or there may be practical limits below that threshold. >> >> >> On 1/18/2023 7:29 PM, David Epstein via use-livecode wrote: >>> How many rows or columns or characters can reasonably be displayed in a >>> LiveCode field? A 1.39 GB text file seems pretty clearly to surpass the >>> limit, but how much do I need to subdivide it? >>> >>> David Epstein >>> ___ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
David. You want to display 1.39 GB in a field? Will it scroll? I made a quick test stack that created a variable with a length of 1.4 GB. No problem. But when I tried to put that variable into a field, LC crashed. When I tried to put 140 MB into a field, same crash. I did not continue to reduce the length of that variable until the field could be loaded. Craig > On Jan 18, 2023, at 7:46 PM, Paul Dupuis via use-livecode > wrote: > > I thought the theoretical limit was 4GB (32bits of characters) but I may be > wrong or there may be practical limits below that threshold. > > > On 1/18/2023 7:29 PM, David Epstein via use-livecode wrote: >> How many rows or columns or characters can reasonably be displayed in a >> LiveCode field? A 1.39 GB text file seems pretty clearly to surpass the >> limit, but how much do I need to subdivide it? >> >> David Epstein >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Maximum field size
I thought the theoretical limit was 4GB (32bits of characters) but I may be wrong or there may be practical limits below that threshold. On 1/18/2023 7:29 PM, David Epstein via use-livecode wrote: How many rows or columns or characters can reasonably be displayed in a LiveCode field? A 1.39 GB text file seems pretty clearly to surpass the limit, but how much do I need to subdivide it? David Epstein ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
