Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Entity selection changes seemingly randomly when trying to edit an annotation property value #346

Closed
csnyulas opened this issue Mar 4, 2016 · 4 comments
Labels
Type: Bug Indicates that Protege is not working as expected

Comments

@csnyulas
Copy link
Member

csnyulas commented Mar 4, 2016

To reproduce:

  • In the "Entities" tab select different entities in different views
  • create an annotation on an entity
  • edit that annotation by clicking on the circle icon.
  • observe that the selection changed to an entity (class or property) that is selected in one of the views, which may or may not be visible at the moment

This behaviour may be related to allowing multiple selections in different views, so there is a chance that a proper fix to #335 may solve this issue, too.

@rsgoncalves
Copy link
Member

It does seem to be related to selections in other views, though this wasn't a problem before. I couldn't replicate the above until I selected topObjectProperty (in the Entities tab). And then when editing the annotation property value of a class, the selection switched to topObjectProperty.

@matthewhorridge
Copy link
Contributor

This seems to be caused by the initialisation of the annotation editor:

AbstractOWLEntityHierarchyViewComponent.setShowDeprecatedEntities

which causes a reload of the tree, followed by a re-selection.

@rsgoncalves
Copy link
Member

Here are the steps I used to reproduce this, using only the Entities Tab:

  • Create class A
  • Add rdfs:comment annotation assertion to A (value is irrelevant)
  • Select owl:TopObjectProperty in the object property view
  • Select class A again
  • Edit rdfs:comment annotation on A
  • Notice the selection switches to owl:TopObjectProperty

@johardi
Copy link
Member

johardi commented Mar 4, 2016

Another steps to reproduce:

  1. Create class A and B in 'Entities' tab,
  2. Switch to 'Individuals by class' tab and select class B in the 'Class hierarchy',
  3. Go back to 'Entities' tab and select class A.
  4. Add an annotation, e.g., rdfs:comment "Blah",
  5. Edit the annotation and the selection immediately "jump" to class B

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Indicates that Protege is not working as expected
Projects
None yet
Development

No branches or pull requests

4 participants