Open bugs

• Sometimes topic tree gets messy if you open and close large (>1000 topics) topic branch fast. This happens mainly with database topic maps as the network traffic slows down the GUI construction. Resolution: Refresh topic tree or reopen topic tree component.
  • It looks like the previous bug has disappeared with Java 6.x.

Peculiar features

Next features are not actual bugs but the novice Wandora user may find them very peculiar:

• When you have locked selected layer and try to edit any topic, Wandora throws com.gripstudios.applications.wandora.topicmap.TopicMapReadOnlyException. To resolve this just unlock the current layer or select another layer.
• Wandora notices automatically if the database user has no write rights to a database topic map and keeps the layer locked even if the user clicks the lock icon in layer stack.
• Wandora does not delete topic even if I select Delete topic. Wandora does not allow topic deletion if the topic is a role topic in any association or a occurrence (text data) type in any occurrence. Delete such associations and occurrences first and try again. Another reason for unsuccessful deletion may be the selected layer. Check that you are have selected right layer that contains the topic. Check also that any other layer does not contain merged topic. Layer distribution vector may help here. You have to delete the topic separately in every layer.
• Wandora does not change topic's base name, variant name or occurrence data. Check if there exists merged topic in above layers. Check also if the topic above already has a base name, variant name or occurrence data with same type and scope. Topic's layer distribution vector may help here. Change the base name, variant name or occurrence data of the top layer or remove base name, variant name or occurrence data of above layers.