Trevor you are brilliant. Now that you put it that way, that is *exactly* what
is happening. The datagrid works so seamlessly it's easy to forget it's not
data I am working with but groups of objects that must be deleted and recreated
as needed.
Bob S
> On Jun 5, 2018, at 21:50 , Trevor
On Tue, Jun 5, 2018 at 5:27 PM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> I suppose I can get around it by using send in time so the actual
> selectionChanged handler finishes before the cascade of form updates
> happens. But if it is a bug and shouldn't be
Hi all.
What I once thought was an endless loop bug I have isolated now to something
else. It seems that when selectionChanged for a datagrid is in the
executionContexts, the dgData must not be changed. I am not sure if this causes
an endless loop internally to the datagrid library or not.
