Re: Encountering slow navigation to a card containing very large fields? Do this one simple trick.

2022-04-17 Thread Richard Gaskin via use-livecode
David V Glasgow wrote: > On 16 Apr 2022, at 8:20 pm, Richard Gaskin wrote: >> >> How many is "many many thousands of lines"? 10k? 100k? More? > > Typically 30,000 to 800,000. What is the user asked to do with 800,000 lines of data? That is, does this need to be displayed? >> Is the data dis

Re: Encountering slow navigation to a card containing very large fields? Do this one simple trick.

2022-04-17 Thread David V Glasgow via use-livecode
> On 17 Apr 2022, at 12:30 am, Bob Sneidar via use-livecode > wrote: > > Yes, I think you have it when you say that displaying text in a field is > processor intensive. Fields are notoriously inefficient at storage. Do all > your processing in memory and then display your results in whatever

Re: Encountering slow navigation to a card containing very large fields? Do this one simple trick.

2022-04-17 Thread David V Glasgow via use-livecode
Hi Richard > On 16 Apr 2022, at 8:20 pm, Richard Gaskin via use-livecode > wrote: > > How many is "many many thousands of lines"? 10k? 100k? More? Typically 30,000 to 800,000. One field wrapped (the imported ‘source’ text) and the other a, unwrapped list of found lines containing a keyword.

Re: Encountering slow navigation to a card containing very large fields? Do this one simple trick.

2022-04-17 Thread David V Glasgow via use-livecode
Hi Jim, The text in fields doesn’t move or change after the initial analysis. the slowdown is just navigating back to to the card containing the fields from from one which doesn’t contain the fields. Cheers David G > On 16 Apr 2022, at 8:46 pm, Jim Lambert via use-livecode > wrote: > >