Table Field click causing freeze and phantom field appears

[adxsoft]

I am using LC 9.02 Community Edition on Mac OSX 10.11.5 and have a table field with the properties show in the attachments. The field consists of lines with two columns of data where column 1 data is tab separated from column 2.

Whenever I am am running the application (Browse Mode) and click into a cell LC seems to freeze. I use Cmd . to stop the application running and switch the pointer tool. Now I can see a small field (Phantom?) in front of the table which wasn't there before. If I delete this field then I can carry on.

So it seems that there is some issue with clicking in a cell of a table field. I think I saw this in past versions and not sure if its a re-introduced problem.

Anybody else seeing this.

[bogs]

That is pretty wierd, something like the issue with cells raugert found, where they would appear randomly if not pre-filled.

I wonder if the two are related

[AxWald]

Hi,

disable the "cell editing", and be sure to never have enabled it anywhere.
This never really worked.

Have fun!

[dunbarx]

You may want to read the entire thread in "Table fields not updating correctly":

viewtopic.php?f=7&t=31452&p=170731&hili ... ly#p170731

Axwald wrote:

disable the "cell editing", and be sure to never have enabled it anywhere.
This never really worked.

This cripples other aspects of the table field. Try to "massage" your field per the later handlers in the above thread. Please write back if that solves the problem.

Craig Newman

[samlrs]

Hi,

disable the "cell editing", and be sure to never have enabled it anywhere.
This never really worked.

Have fun!

interesting, and what was this function actually intended for?????

[dunbarx]

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

[samlrs]

Thanks for the expnanation