The callback attached to the table cell is called after DBListView.viewWillAppear.
As a consequence, open/close database is not as intended.
It happens that a modification is not stored.
Note: Maybe related? In the console window I see a message like:
[Common] _BSMachError: port 8203; (os/kern) invalid capability (0x14) "Unable to insert COPY_SEND"
1) The error message "... BSMachError: ...Unable to insert COPY_SEND" is not related. The race condition occurs although the error message is not shown.
2) Example scenario:
in the database list, press "Bearbeiten", then select a database.
modify the difficulty, but keep the cursor in this field.
press 'back'.
select the same database to check its values.
Expected: the difficulty is on its new value.
Observed: the difficulty is on its old value.
Note: As we don't offer a 'cancel' option at this screen, the behaviour could be seen as intentional. It allows the user to cancel the current edit.
Note 2: the 'rename' field does not follow this logic - it is always modified at once.
Last edit: Christa Runge 2020-08-08