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

Shift key c triggers autocompletion instead of allowing the user to enter uppercase C #637

Closed
samsontu opened this issue Mar 30, 2017 · 1 comment
Assignees
Labels
Status: Fixed Added to indicate that a closed issue represents a bug that has been fixed Type: Bug Indicates that Protege is not working as expected

Comments

@samsontu
Copy link

Protege 5.2
To reproduce:

  1. Supposed we had entered "contains some WalkersShortbreadItem" as a class expression in the most recent operation somewhere
  2. Now we want to specify that the individual is an instance Country
  3. In the class expression dialog box, holding down shift key to type C triggers autocompletion for 'contains some WalkerShortbreadItem' instead of allowing a user to enter 'C'.

Perhaps autocompletion should be case-sensitive, since OWL is case-sensitive.

@csnyulas
Copy link
Member

This may be a bigger issue. Another user (on a machine running Ubuntu) had problems entering a property chain expression in the property chain editor. Whenever he started entering the property name the auto-completion (or more specifically the history suggestion) automatically filled in the content of the field, and he was not able to enter the expression that he was trying write. Not even with copy paste did it work. Somehow the auto-completion overwrote what the user was trying to enter. Please feel free to create a separate issue for this if it turns out that it is a different problem.

@matthewhorridge matthewhorridge added the Status: Needs Triage Should be the default status for issues that have been acknowledged, but not yet processed. label Jan 15, 2019
@matthewhorridge matthewhorridge self-assigned this Mar 18, 2019
@matthewhorridge matthewhorridge added Type: Bug Indicates that Protege is not working as expected Status: Fixed Added to indicate that a closed issue represents a bug that has been fixed and removed Status: Needs Triage Should be the default status for issues that have been acknowledged, but not yet processed. labels Mar 18, 2019
@matthewhorridge matthewhorridge added this to the Protégé 5.6.0 milestone Mar 18, 2019
matthewhorridge added a commit that referenced this issue Mar 18, 2019
It is also a workaround for aggressive expression expansion related issues.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Fixed Added to indicate that a closed issue represents a bug that has been fixed Type: Bug Indicates that Protege is not working as expected
Projects
None yet
Development

No branches or pull requests

3 participants