Table field locks Livecode

[Simon Knight]

I am using LC 9.6.13 rc 1 on Mac OS Sonoma.

I created a new blank default stack and added a table field. Next I set the tabs to 150,0 and adjusted the width of the table field to display a single column. Then I manually added text to the cells e.g. row 1, row2, row 3, row 4 etc. So far so good. Note at this point the new stack has not been saved.

Next I attempt to edit a populated row. The field editor is displayed and initially I am able to select an edit point but at about this stage Livecode freezes and requires a Forced Quit. However, if the stack is saved to disc the problem does not occur. This is not a one off as I am able repeat the freeze.

I have not filed a bug report as it may be an issue with my hardware. I wonder if anyone else is willing to repeat the test?

best wishes

S

[bn]

Hi Simon,

could you post a sample stack with your tableField. That way it is easier to reproduce the bug.

If LC stops responding then you can type command or control + "." to exit the endless loop that I assume is happening.
If you type into the message box

Code: Select all

global gRevDevelopment; put true into gRevDevelopment

then the debugger will show you the offending handler/code when hitting control or command + "."

Kind regards
Bernd

[Simon Knight]

Hi Bernd,

Unfortunately the fault does not appear once the stack has been saved and then reloaded. The fault is infrequent so difficult to pin down. I have just seen the fault again and using cmd stop does break the freeze but on most runs the fault does not appear. I'm not even sure if changing the tab stops has anything to do with the issue I am seeing.

best wishes

Simon

[bn]

Hi Simon,

I can reliably send the tablefield into an endless loop when I set the tabWidths to 120,0 and see the second column. When I click into the second (non existing) column then it triggers the endless loop. Saved or not saved.
There are a lot of quirks in the tableField, some of which I have reported, some have been fixed. But the tableField was not really prepared for the advent of tabWidths, i.e. the option to limit the number of columns by setting the last item of the tabWidths to 0.

It probably has to do with that.

I am not sure the tableField is a solid control when used with cell editing.

Kind regards
Bernd

[Simon Knight]

Hi Bernd,

Thanks for taking a look and confirming what I am seeing. I'm not sure its worth a bug report given that the focus is all on Create.

best wishes

Simon