Hmmm. Food for thought both!
Loading I just use
put URL ("file:" & theFilePath) into tdata
I have always assumed that reading as binary is only for data that isn’t text.
I’ll try that. If I want to display some or all of the file in a field, do I
need to process the data read as a binary, or can I just put it into a field?
So far I have worked on the principle that users should be able to see the
effects of their searches, etc, so have defaulted to field. Maybe I could
store part of the list in the field (and swap in/out out as users scroll
through) but do the main storage and heavy lifting within a custom property?
Thanks very much for the suggestions.
Cheers,
David G
> On 1 Jul 2020, at 5:15 pm, Klaus major-k via use-livecode
> <[email protected]> wrote:
>
> Hi David
>
>> Am 01.07.2020 um 18:10 schrieb Richard Gaskin via use-livecode
>> <[email protected]>:
>>
>> David V Glasgow wrote:
>>
>>> Loading the plain text list of URLs from file is slowish, but more
>>> importantly, for some time gives no indication that the file is
>>> loading.
>>
>> Are you reading the file as text or binary?
>> I would imagine reading as binary would be more efficient since it's a
>> straight pull from disk, without the content alterations text-read does.
>>
>> --
>> Richard Gaskin
>
> and unless REALLY neccessary, store the data in a custom property instead of
> a field.
>
>
> Best
>
> Klaus
>
> --
> Klaus Major
> https://www.major-k.de
> [email protected]
>
>
> _______________________________________________
> use-livecode mailing list
> [email protected]
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
