Open bugs
From WandoraWiki
(Difference between revisions)
| Line 1: | Line 1: | ||
* 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. | * 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 | + | ** It looks like the previous bug has disappeared with Java 6.x. |
== Peculiar features == | == Peculiar features == | ||
| Line 7: | Line 7: | ||
* 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. | * 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. | ||
Revision as of 12:04, 29 June 2007
- 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.
