|
|
| (56 intermediate revisions by one user not shown) |
| Line 1: |
Line 1: |
| − | * The logging pop-up generates sometimes NullPointerException. This bug has no effect on Wandora except annoying exception report to the shell console window (which is invisible if you started Wandora with '''Wandora.exe''').
| + | 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]. |
| − | * 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.
| + | |
| − | | + | |
| − | | + | |
| − | == Resolving problems and bug reports ==
| + | |
| − | | + | |
| − | If you encounter problems using Wandora | + | |
| − | | + | |
| − | * Save your current project and close Wandora.
| + | |
| − | * Start Wandora with shell scripts found in '''bin''' folder. '''Wandora.bat''' is the default script you might want to try first. if you have a feeling that the problem was caused by insufficient memory you can also try '''Wandora-large.bat''' or '''Wandora-huge.bat'''. Starting Wandora with script opens a shell window beside the Wandora window. Wandora writes extra logs to the shell window.
| + | |
| − | * Load your project back to Wandora.
| + | |
| − | * Repeat the action producing problems.
| + | |
| − | * Check the console shell window. If shell window contains suspicious text fragments such as Java exceptions please copy the text and send it to us by email to {{wandora email address}} and we'll try to fix the problem. Please remember to attach general description of the action producing errors. Also, include '''[Wandora]''' to your email title. This ensures your valuable report is not trashed by our spam filter.
| + | |
| − | | + | |
| − | == 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.
| + | |
| − | | + | |
| − | ===I am not able to (re)configure a layer===
| + | |
| − | Only database layers can be reconfigured. When layer is reconfigured, layer's database settings such as database host, user name and password are updated. If you wish to rename the player, please use '''Rename layer'''.
| + | |
| − | | + | |
| − | ===I can't see topic's associations, classes, instances, names, occurrences in topic panel===
| + | |
| − | Check that you have toggled the topic element visible in '''View''' menu.
| + | |
| − | | + | |
| − | ===Wandora does not 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.
| + | |
| − | | + | |
| − | ===Base name does not change when I make base name with subject identifier===
| + | |
| − | Generating base name with subject identifier does not change existing base names. To force base name generation, remove old base names before base name generation. To remove base names
| + | |
| − | | + | |
| − | * Select all topics
| + | |
| − | * Start '''Topics > Base names > Remove base names...'''
| + | |
| − | | + | |
| − | ===Topic is red!===
| + | |
| − | Topic is not located 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. | + | |
| − | | + | |
| − | ===Topic is [null]===
| + | |
| − | This happens with association tables when association has no player with expected role. Wandora tries to optimize association visualization by placing multiple similar (=same association type) associations into a single topic table. Now, if you have two associations with same type but different roles, the association table has columns for all roles found in these association and the column contains '''[null]''' if the association has no player with column role.
| + | |
| − | | + | |
| − | ===Topic is [removed]===
| + | |
| − | You probably see this most often in Finder's result set. When topic is shown as '''[removed]''', the topic table cell contains removed topic. Topic may have been removed explicitly by '''Delete topic''' operation or implicitly by merging the topic to another. If you perform the Finder search again the result set is updated and should not contain '''[removed]''' topics.
| + | |
| − | | + | |
| − | ===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'''.
| + | |
| − | | + | |
| − | ===I live in Sweden and would like to see Swedish as the first variant name type (occurrence type)===
| + | |
| − | Variant name types are now arranged in alphabetical order. To change the order open topic '''Language SE''' under '''Wandora language''' and add '''_Swedish''' as a '''Sort name''' for the topic. Now Swedish locates before English, Finnish, and Lang.indep. in sort array.
| + | |
| − | | + | |
| − | ===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.
