Bugs

  • [2.90] A ‘large result - do you want to stop?’ warning type thing is needed for the InfoPane display of history relations for the browse focus. Each concept in the descent of 370136006|Namespace concept (namespace concept)| can have many thousands of concepts that have a MOVED_TO relationship to it. Clicking on such a namespace concept causes SNOB to go away for a long time to retrieve them if display of history relationships is selected as an option.
    Fixed in 3.00.01
  • [2.60] The order in which you import the various files that make up a Xmap specification appears to be critical (must be crossmapsets before crossmaptargets before crossmaps). However, if you import them in the wrong order e.g. using an import script, the import will complete without error but the Xmaps are not actually visible.
  • [2.01.00] Changing the global browse date refocusses the browser on the root concept. Would be better if it remained focussed on the current browse concept.
  • It would be a very good idea to popup a warning when a search terminates because the Max number of returned concepts limit has been hit.
  • The ‘save hierarchy as bitmap’ function sometimes seems to take its screengrab before completion of the redraw that happens after the pop-up menu disappears, so that there’s a large white blank rectangle somewhere on the right hand side of the resulting screengrab. Unfortunately I can’t reproduce exactly when it happens.
  • If you copy a string from another application and then paste it into the SNOB search box, you often get a control character pasted in instead of the actual text (it appears as a single rectangle box character) the first time you try to paste it in. This is tricky to reproduce exactly, but it happens a lot.

Click here to see the list of fixed bugs

Discussion

Sometimes, you think you have found a bug, which is actually a feature ;-), a misunderstanding, or just a matter of the wrong settings. Below, I shall collect these and point you to the relevant FAQ.

  • If SNOB is instead distributed with a pre-built DB this isn’t appropriate, and a casual user might accidentally delete the distributed DB build thinking they were going to be opening it.
    If you distribute SNOB with a pre-built DB you should include a setup.xml file your distribution.
 
snob/bugs.txt · Last modified: 2009/12/22 12:33 by eh
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki