[protege-releases] Protege 4.2 beta update (build 278)

There's a new Protege 4.2 beta build available on our website.

Link for registered users:

http://protege.stanford.edu/download/registered.html#p4.2

New users, please register before downloading:

http://protege.stanford.edu/download/register.html


Release Notes
--------------------
- Fixed a bug that caused the Usage view to fail with a 
NullPointerException if it was displayed before an entity of the 
appropriate type was selected. For example, if a user opened an ontology 
and selected the class usage view before selecting a class, the view 
would fail. The view could then only be restored by resetting the UI or 
restarting Protege.

- The rename multiple entities tool (Refactor | Rename multiple 
entities...) no longer has problems renaming URIs that include 
characters with special meanings for a regular expression search.

- Interrupting a reasoner now works properly with two provisos. First, 
some reasoners will not respond to an interrupt. This is a reasoner 
problem and we can't fix that. Second, after the interrupt, Protege will 
continue to use the reasoner. This will be dealt with in the next 
version of Protege.

- Added a Stop reasoner menu item to allow users to stop a reasoner 
(Reasoner | Stop reasoner). Previously, the best method of stopping a 
reasoner was to select a different default reasoner type.

- Changed the default configuration of the Individuals tab in response 
to some comments on the p4-feedback mailing list. The previous 
configuration could be confusing because all the views of the collection 
of individuals were filtered by the selected class.

- Centralized and improved the handling of vacuous inferred results. 
Previously, several inferred views would be cluttered with a large 
number of trivial results. Now this clutter has been somewhat trimmed 
and the trimming is applied consistently across the user interface.

- Fixed a problem with new entity preferences where it was possible for 
the generated fragment to use an auto-generated ID, but the label 
provided by the user was not used.

- Fixed a bug where the Object/Data restriction creator sometimes failed 
to allow valid input.

- Fixed the Add to ontology button in the DL Query tab.


Best Regards,
The Protege Team

_______________________________________________
protege-releases mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/protege-releases

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03