Oooohkaaaay... So the problem is not calling selectionChanged while another selectionChanged is running. The problem is setting the dgData (or dgText I will assume) while a selectionChanged handler is running. I remember I tracked that down before this. Setting the dgData is obviously triggering selectionChanged from within the datagrid library.
Soooo... I AM calling this a bug!!! I will try to put together a recipe for this and submit it. Bob S > On Jan 24, 2019, at 11:29 , Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > For those interested, I've had a bit of a revelation concerning datagrids and > the selectionChanged handler. Here's the problem. > > I use datagrids extensively. I have code in my selectionChanged handlers in > the datagrids that update the card objects; fields buttons etc. It's > convenient for me therefore when I change the hilited line by script to > simply send selectionChanged to the appropriate datagrid. This however has > uncovered an anomaly (I don't say bug) where an endless recursion can occur > in the datagrid library if selectionChanged gets called again while the first > is still executing. _______________________________________________ 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
