Adding activity via hamster isn't immediately reflected in the UI

[matclab]

For now we have to wait that argos refreshes the plugin (at most 1m) for the activity status to be reflected in the UI.

This is probably not a great problem, but it would be nice to be able to correct the problem.

One way to prevent this, would be to make hamster add command blocking. We could then do a touch ~/.config/argos/hamster.1m+.py plugin to force the refresh. But I don't know how to do it without modifying hamster.

Any other idea ?

[GeraldJansen]

A partial work-around would be renaming to hamster.5s+.py or hamster.2s.py to greatly reduce the delay. On my system updating every 1s increased cpu usage slightly, but 2s or more is barely noticeable. However, this is not really a satisfactory solution.
[ed.] Forget this, it annoyingly refreshes while you have the menu open.

[matclab]

Closed with merge of #6 : 04811dd

[matclab]

Re-openning as adding an activity via the "show overview" doesn't lead to the UI being updated.