Importing a fligh-track into MSCOlab does not update the versions in the version history automatically

[joernu76]

After importing a flight track, it was not updated to MSColab. Changing a table view longitude coordinate updated then the full plan to the server.

Desired behaviour:
After import, a new version should be generated immediately.

[ReimarBauer]

@joernu76 I can't reproduce, I created a devel category and tried there on the devel1 OP.

[ReimarBauer]

Please provide more details

Refresh on the version history shows the updates

example_ftml_import.webm

[joernu76]

OK, I had a closer look. The Version Window - in contrast to other View windows - is not automatically updated.
This is surprising and thus not Pythonic. :-)
Manually refreshing helps indeed.
Is there a design reason for this?

[ReimarBauer]

The default is to look on named versions, you need to toggle to All versions too.

To get this updated it requires to implement a handler which act on 'file-changed' (because any user can update), signal_reload.

It was not implemented because it does make on many edits the table flicker.

When implemented that functionality should be covered by a test too.