Topicmaps management oddities

[jri]

Topicmaps plugin:

• Topicmaps that are reloaded are not put in the topicmaps cache. That happens on login/logout. As a result that topicmap is not subject of global topic updates/deletes.

• Once a topicmap is deleted the "was this the last topicmap?"-check is not accurate (as it is based on checking the topicmaps cache, not the DB). As a result another bogus "untitled" topicmap might be created.

[Jörg Richter]

Fix topicmaps management oddities.

Close #520

• Changeset: 1717c740e3e54d7b80603b75a00be94fa3ad07b9
• URL: ​https://github.com/jri/deepamehta/commit/1717c740e3e54d7b80603b75a00be94fa3ad07b9

[Jörg Richter]

Topicmaps: fix display of initial topicmap (#520).

When the initial Webclient URL contained a topic reference dm4c.do_select_topic() was called twice. At time of the first call the topicmap might not yet be displayed (due to asynchronicity) which under some circumstances caused problems.

Now dm4c.do_select_topic() is called only once and at a time when the topicmap is guaranteed to be displayed.

See #520.

• Changeset: 7be27b314e5f68cfa071ff8c6f03994229ddc949
• URL: ​https://github.com/jri/deepamehta/commit/7be27b314e5f68cfa071ff8c6f03994229ddc949

[Jörg Richter]

Topicmaps: fix display of initial topicmap (#520).

When the initial Webclient URL contained a topic reference dm4c.do_select_topic() was called twice. At time of the first call the topicmap might not yet be displayed (due to asynchronicity) which under some circumstances caused problems.

Now dm4c.do_select_topic() is called only once and at a time when the topicmap is guaranteed to be displayed.

See #520.

• Changeset: 7be27b314e5f68cfa071ff8c6f03994229ddc949
• URL: ​https://github.com/jri/deepamehta/commit/7be27b314e5f68cfa071ff8c6f03994229ddc949