Skip to content

Activate Debugging Buttons after Exception occurs

If an exception during a debuggin session occurs the buttons do not get active again.

The problem can in the following way:

Use 0.1.3.BETA.

Load the miniTambis-Full[1] ontology from the URL https://raw.githubusercontent.com/ha-mo-we/Racer/master/examples/owl/tambis-full.owl select Pellet and start a new session.

This causes an exception. But the buttons are not reactivated (the deactivation has been implemented in the development cycle for 0.1.3.BETA to prevent double clicking buttons after a session is started).

[1] http://ac.els-cdn.com/S1570826805000260/1-s2.0-S1570826805000260-main.pdf?_tid=01583488-f2be-11e6-ac4b-00000aab0f6b&acdnat=1487081036_ee63756c052f2b5a64a8cfb01dbba196