Bob is probably right about the fact that you may run out of functional power with a table field. But I use them whenever I can, since they are much simpler and easier to manage.
A phantom field is indeed created when you double-click on a "cell". Put this in the card script: on selectionchanged put the name of the last field end selectionchanged Double click, and you can see that field. This may give you a pathway to fooling around with the table field workings. Craig NEwman -----Original Message----- From: David Epstein <dfepst...@comcast.net> To: use-livecode <use-livecode@lists.runrev.com> Sent: Fri, Feb 21, 2014 11:00 pm Subject: Edit cell in basic table field 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
