Okay I found a quick workaround. I check to see if the dgText of the datagrid is empty (which it is) before getting the dgData. This is very odd, and makes me nervous about chaining behaviors with datagrids.
Bob S > On Sep 12, 2018, at 08:14 , Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Hmmm... oddly this does not happen in a basic test stack. I am executing the > commands in a behavior though, and that behavior is inline with the datagrid > behavior. If that is the culprit, it's gonna be a beatch fixing it. > > Bob S > > >> On Sep 12, 2018, at 08:08 , Bob Sneidar via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> Hi all. >> >> Something is happening with getting the dgData of a datagrid. If I am >> stepping through code that gets the dgData of an empty datagrid, I get an >> array whose only key is 0 and there is no value. This never happened before. >> This is problematic for me because I often simply test to see if the >> variable is an array and proceed accordingly. >> >> If anyone else can reproduce this, I will post a bug report. MacOS X 10.13.6 >> LC 9.0.1 rc1. >> >> Bob S _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
