Please see attached minimal stack with a table field which has the following script:
Code: Select all
on rawkeyup
answer "rawkeyup"
end rawkeyup
on textchanged
answer "text changed"
end textchanged
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Code: Select all
on rawkeyup
answer "rawkeyup"
end rawkeyup
on textchanged
answer "text changed"
end textchanged
Code: Select all
on rawkeyup
answer "rawkeyup"
end rawkeyup
Code: Select all
on textchanged
answer "text changed"
end textchanged
Not MAY, it DOES!richmond62 wrote: ↑Sun Nov 01, 2020 2:39 pmLC may create a temporary field to bung text in the cell of a tableField when text is entered for the first time.
Seriously?richmond62 wrote: ↑Sun Nov 01, 2020 2:39 pmBut what happens when the user attempts tp append text to the first text?
Hi.
Make a table field. If you simply click inside any "cell" and type, there is little to distinguish between having cell editing enabled or disabled.
Until you hit return in one of those "cells". Remember that a table field is just a field with certain properties. Having cell editing enabled allows the field to create a new "phantom" field, overlying a cell, where one can enter data. This is then loaded into the "cell" of interest. If you hit return, the cell is loaded, and the phantom field moves down one row. But if cell editing is disabled, that return is simply included "normally", and a blank row appears.
The intent of a table field really requires that editing be enabled. Did you read that thread I mentioned just a couple of posts above? It says it all.
Craig