Hmm. There is a potential issue that would need to be worked around. The
field name is the same whether one has a single table field or 12. Perhaps
watching focus changes? I'm back to thinking there is a property that
tracks which field to update on close of the editing overlay. For a single
table though, the first idea works great.
Time to poke some more.
On Wed, Feb 14, 2018 at 9:28 AM, Mike Bonner <bonnm...@gmail.com> wrote:
> a table field ISN'T a single field, its a field bundled with an extra
> "editing" field that pops up as an overlay. I figured there had to be a
> way to pass the cell data back to the field proper, and poked around till I
> found out that the transfer mechanism is the name of the overlay field. I
> was worried that it was a property and that I'd have to dig around much
> deeper to find it, but turns out it was much more straight forward than I
> On Wed, Feb 14, 2018 at 9:24 AM, dunbarx via use-livecode <
> firstname.lastname@example.org> wrote:
>> You know, I have given advice many times to people trying to find the
>> selected field in a DG. The target is always of the form, for example,
>> "field Col 3 0005".
>> But how does the focussedObject return similar data in a table field? The
>> fact that is does is marvelous indeed, but I never would have found that,
>> and if I checked the dictionary, i definitely never would have thought of
>> A table field, after all, is but a single field, and the focusedObject
>> to return a control reference, not a non existent "cell" gizmo.
>> At the very least, the dictionary should include this valuable variant of
>> the property. And the user guide should have it in bold.
>> Sent from: http://runtime-revolution.278305.n4.nabble.com/Revolution-
>> use-livecode mailing list
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription