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

2022-04-21 Thread Bob Sneidar via use-livecode
Let me know off list if you want to have a look at the handlers I have written for getting data from a datagrid array into a memory database and back again so your queries can be more efficient. Bob S > On Apr 21, 2022, at 04:50 , David V Glasgow via use-livecode > wrote: > > > Thanks to

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

2022-04-19 Thread David V Glasgow via use-livecode
Maybe context would help. I receive digital evidence from police Hi Tech Crime Units, consisting of lists/tables of messages, search histories, web histories, files downloaded, etc etc. These relate to online activities of alleged internet offenders. Some consist of data relating to a few mont

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: > >

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

2022-04-16 Thread J. Landman Gay via use-livecode
So fields are snakes and datagrids are mice. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On April 16, 2022 6:32:19 PM Bob Sneidar via use-livecode wrote: The Datagrid eats the Elephant, “One Bite At a Time.” The field tries to eat th

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

2022-04-16 Thread Richard Gaskin via use-livecode
David Glasgow wrote: > I have a card (A) with two fields in separate groups. Field 1 > contains many many thousands of lines of text which are filtered > for keywords and the results displayed in field 2 (which can also > be many thousands of lines). The user can navigate to a separate > card (