Yes. It’s called “use a data grid instead”. Table objects are simple fields that pretend to act as tables. Nothing beyond the messages a field gets are sent to a table field. It is JUST a field. That’s all.
Datagrids on the other hand, are a complex group of fields and behaviors that make up the whole. Lots of messages get sent to a data grid that allow you to fine tune it’s behavior. And if that is not enough, you can “clone” the behavior to a button of your choosing, and then modify that particular data grid’s behavior to your heart’s content! I was a little put off by data grids at first, but necessity drove me to investigate their capabilities and now I simply cannot build an app that needs tables without using them. Bob On Feb 21, 2014, at 19:59 , David Epstein <dfepst...@comcast.net> wrote: > If I check "basic table object" in the field property inspector, and check > "Edit cell," clicking on the table field causes a small unlocked field to be > created at the cell's location, which on tab or arrowkey has its contents > written to the cell. > > Is there some way to have a script trap the relevant information about what > is going on, e.g., that a cell has just been "opened for editing", that a > cell has just been edited, which cell it is, etc.? > > I assume that this "Edit Cell" activity is governed by a script that is > reading a custom property, but I see no indication that the field actually > has such a property or where the script is. > > Many thanks. > > David Epstein > _______________________________________________ > 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
