In those cases the selection change is a side effect of something else. The user isn’t changing the selection, the user is doing something else that changes the selection. As this thread covered, the textchanged message is sent.
I think it fully makes sense to only send one of those two messages. Otherwise just about every key press inside a field would generate 2 messages. Thanks, Brian On Oct 29, 2019, 10:59 AM -0400, Paul Dupuis via use-livecode <use-livecode@lists.runrev.com>, wrote: > On 10/29/2019 9:47 AM, Brian Milby via use-livecode wrote: > > It looks like selectionChanged only reacts to explicit user events (mouse > > click or cursor moved via keyboard navigation). > I, for one, would consider user-driven pasting of text or user driven > drag and drop to be 'explicit user events', so I would still consider > this an engine bug rather than a documentation bug. > > _______________________________________________ > 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 _______________________________________________ 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
