Okay I found another obscure instance of the same thing and fixed it. I have learned a valuable lesson: Bail from handlers when there is no point proceeding. An empty value for the dhHilitedIndex in this particular handler produced the same visible results, but ended up setting my array (which the whole form is based upon) to empty. I really need to be more disciplined in my coding habits.
I still would LOVE to see that variable watch feature fixed again though. That is insanely useful! Bob > yup found one instance of that. Have to be careful though because I have a > second datagrid that is populated with related table data and uses the values > in the array in it's own query. <sigh> I just have to pore through the code. > > Bob > > > On Jan 24, 2012, at 1:22 PM, Phil Davis wrote: > >> Hmmm. You probably already tried this, but... can you check for a non-empty >> value in dgHilitedIndex before allowing the 'put... into...' to proceed? Of >> course that's still a problem if it happens in 14 dozen different places. >> >> Maybe put the actual setting of the array inside a setProp handler, so your >> setprop handler script can examine the 'set to' values before allowing it? >> >> Sounds frustrating indeed. >> >> Phil >> > _______________________________________________ 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
