I forgot to mention : for each query, apart from populating the fields
of the
sub-groups with new content, a couple of custom properties of each
sub-group
is set (or modified) too.
Le 2026-05-12 13:55, jbv via use-livecode a écrit :
Le 2026-05-12 13:13, Bob Sneidar via use-livecode a écrit :
OIC. NOT a datagrid. Just a custom group. What makes a datagrid more
efficient is that the fields and controls in the datagrid are only
created and populated for the visible rows. It sounds like you are
populating ALL the fields and yes, when you change cards Livecode has
to “draw” all those fields.
I cannot imagine a reason why a datagrid would not work for this.
Bob S
Believe me, I tried with the datagrid in the first place, and it was
much slower than what I built.
Besides, as I already explained, the delay occurs only when moving from
one card to another for the
first time. After going back and forth between the 2 cards a couple of
times, the switch between
cards is instantaneous. But when a new query is sent from one of the
cards and the fields are
populated with new content, then the delay happens again.
That's why I suppose that the card controls and their contents are
stored somewhere by the engine
before changing cards.
_______________________________________________
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
