Broken table field in v8.1
Posted: Tue Sep 27, 2016 10:53 pm
On a new card make a table field. A handful of columns wide will do. A handful of rows would be nice.
If I click in a "cell" on the left side of the table field, whatever I type will go into that cell. If I click on a cell on the right side somewhere, the data goes into a cell somewhere on one of the leftmost columns, usually column 2, and several rows down. Oh yes, whatever I type will append, not replace any data already in the (unknowable) target cell. No problem duplicating this in new sessions. I bet anyone can do it.
I cannot even smugly say I am going back to v6, because over there, if I have the following handler in the field script:
I can reliably crash v.6.9. Anyone can do it. No handler, no problem.
I happen to like table fields. Anyone else see this before I file a report?
Oh yes, at least in v6, the phantom field that opens for editing overlies the "cell" of interest. As I expected, in v8, the phantom is offset, overlarge, and clunky. I want to migrate, but will not. I do not feel at home in any way with v8, for many reasons, though mostly cosmetic.
Craig Newman
If I click in a "cell" on the left side of the table field, whatever I type will go into that cell. If I click on a cell on the right side somewhere, the data goes into a cell somewhere on one of the leftmost columns, usually column 2, and several rows down. Oh yes, whatever I type will append, not replace any data already in the (unknowable) target cell. No problem duplicating this in new sessions. I bet anyone can do it.
I cannot even smugly say I am going back to v6, because over there, if I have the following handler in the field script:
Code: Select all
on mouseUp
put the clickfield
end mouseUp
I happen to like table fields. Anyone else see this before I file a report?
Oh yes, at least in v6, the phantom field that opens for editing overlies the "cell" of interest. As I expected, in v8, the phantom is offset, overlarge, and clunky. I want to migrate, but will not. I do not feel at home in any way with v8, for many reasons, though mostly cosmetic.
Craig Newman