Open bugs

• The logging pop-up generates sometimes NullPointerException. This bug has no effect on Wandora except annoying exception report to the shell console window.
• Printing a topic relies on Java's JTextPane. It looks the print has some problems with letter spacing. Paging is also little problematic.
• 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 along Java 6.x.

Peculiar features

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

• The layer is red! This happens only with database topic map layers. Wandora is not able to connect the given database. Right click the layer, select Configure layer... and correct database settings.
• When I try to edit a topic Wandora throws com.gripstudios.applications.wandora.topicmap.TopicMapReadOnlyException. You have locked current layer. To resolve this just unlock the current layer or select another layer.
• I try to unlock a layer but it doesn't unlock! This happens only with database topic map layers. Wandora notices automatically if the database user has no write rights to the database topic map and keeps the layer locked even if the user clicks the lock icon in layer stack. To resolve problem reconfigure your layer and change the database user to another or change the database user rights.
• Wandora does not delete topic even if I select Delete topic. Wandora does not allow topic deletion if the topic is a role in any association or an 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 the topic is included in selected layer. 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 a merged topic in layers above. Check also if the topic above already has a base name, variant name or occurrence data with the 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 layers above.
• Base name is red! The base name locates in merged topic but not in current layer. Changing the base name now does not change viewed base name but adds base name to the topic in current layer. Depending on the layer order the effect is
  • Base name does not change but stays red. The merged topic above overrides the topic in current layer.
  • Base name changes and the color of the base name changes to black. The merged topic is below current layer and you have overriden the base name in merged topic. Toggling the visibility of current layer changes the base name to the base name found in layer below.
• Topic is red! Topic does not locate in current layer! Editing the topic now creates merged topic to the current layer.
• I am not able to delete topic's subject identifier. Wandora does not allow SI deletion if topic has only one SI. Add second SI to the topic and remove the first one.
• I try to add association but the association editor window does not work. Wandora has two association editors. You probably opened the schema association editor and have not defined required schema associations. Try starting the schemaless association editor selecting Add schemaless association.
• Oops, I made a mistake. Is there any kind of Cancel or Undo in Wandora? Sorry. Not at the moment. Although we have been thinking it over. Maybe in future releases.