On Fri, Sep 23, 2022 at 4:44 PM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Letting the engine do it for you is always faster.
>
Interestingly, *just* getting the names and ids for a 1500 card stack is
only about 15 times faster using the functions rather than a
Yep, I'm aware of cardnames. I don't have any memory of why I wrote it this
way -- maybe I didn't trust the ordering of cardnames and cardids? Or maybe
it made more sense to collect by hand than to stitch together the values?
Or maybe I just sucked at that moment in time.
gc
On Fri, Sep 23, 2022
The docs in the dictionary may not be complete, yet. I filed a report about
it, but I don't know if they're all done or not.
On Fri, Sep 23, 2022 at 2:11 PM Tom Glod via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Thanks Klaus,
>
> Its strange that it didn't occur to me to check
Are you familiar with the cardnames function? Letting the engine do it for
you is always faster. That doesn't answer your question though.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On September 23, 2022 5:46:24 PM Geoff Canyon via
On Fri, Sep 23, 2022 at 11:08 AM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 9/23/22 10:40, J. Landman Gay via use-livecode wrote:
> > It may be related to the size of the stack. LC would have to load it all
> > into memory before checking the cards. Also, do the
My test stack had over a thousand cards in it, and was still fast checking
the 1000th card.
I've now added a field to each of a thousand cards and stuck text in it;
the stack is over 12MB and still much faster than Navigator, which is under
1MB.
Lock Messages does nothing as far as I can tell.
Thanks Klaus,
Its strange that it didn't occur to me to check there, I assumed it was not
updated. :D
My bad.
Thanks.
Tom
On Fri, Sep 23, 2022 at 11:47 AM Klaus major-k via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Hi Tom,
>
> > Am 23.09.2022 um 01:32 schrieb Tom Glod via
On 9/23/22 10:40, J. Landman Gay via use-livecode wrote:
It may be related to the size of the stack. LC would have to load it all
into memory before checking the cards. Also, do the results change if
you lock messages?
You also do a *lot* of work on both opening the stack and opening the
It may be related to the size of the stack. LC would have to load it all
into memory before checking the cards. Also, do the results change if you
lock messages?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On September 22, 2022
Hi Tom,
> Am 23.09.2022 um 01:32 schrieb Tom Glod via use-livecode
> :
>
> Hello Folks,
>
> I'm wondering if there is any official documentation for the polygrid and
> polylist widgets.
> Like a place that tells you what messages the grid listens to and etc.
> Something in written form?
yes,
Hmm, this is what "the stacks" returns for me:
/Users/gcanyon/Desktop/nav tester 0.004608
/Applications/LiveCode
9.6.8.app/Contents/Tools/Toolset/palettes/script-editor/revscripteditor.rev
0.272558
/Applications/LiveCode
Something weird happened to my post.
I modified your handler to access only those stacks that appear when calling
the function “the stacks”. In all those cases, the return time was only a few
tenths of a second.
But “revNaviigator” does not appear on that list. So there must be a longer
Geoff.
I get over 5 seconds for the “revNavigatior”
So I modified your handler just a bit, to only a
But “revNaviigator” does not appear on that list. So there must be a longer
pathway for LC to find a stack that certainly must be in memory, but that does
not appear in the “stacks” list?
13 matches
Mail list logo
