|
|
| (89 intermediate revisions by one user not shown) |
| 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.
| + | Wandora is developed actively. We know the software is incomplete and contains bugs. We appreciate bug reports and bug fixes. If you encounter problems using Wandora, please send a report to us using email address {{wandora email address}} and we'll try to fix the problem. Before submitting an error report, please check Wandora's console shell window. If the shell window contains suspicious text fragments such as Java exceptions, please copy the text and send it too. Please remember to attach a general description of the actions generating the error. Moreover, include '''[Wandora]''' to your email title. This ensures your valuable report is not trashed by our spam filter. You may also report the bug in [http://www.wandora.net/wandora/forum/index.php Wandora forum] or our [https://github.com/wandora-team/wandora Github repository]. |
| − | ** 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:
| + | |
| − | | + | |
| − | * '''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 a 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 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.
| + | |
| − | * '''Base name is red!''' The base name locates in merged topic that is 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 seems to override topic in current layer.
| + | |
| − | ** Base name changes and the color of the base name changes to black. The merged topic seems to be below current layer. If you now toggle the visibility of current layer you may see base name changing 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 opened 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.
| + | |
Wandora is developed actively. We know the software is incomplete and contains bugs. We appreciate bug reports and bug fixes. If you encounter problems using Wandora, please send a report to us using email address support 
wandora.org and we'll try to fix the problem. Before submitting an error report, please check Wandora's console shell window. If the shell window contains suspicious text fragments such as Java exceptions, please copy the text and send it too. Please remember to attach a general description of the actions generating the error. Moreover, include [Wandora] to your email title. This ensures your valuable report is not trashed by our spam filter. You may also report the bug in Wandora forum or our Github repository.
