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.

Sign up for GitHub

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

Jump to bottom

Add "No to All" option for Resolve Missing Imports dialog #707

Closed
marco-brandizi opened this issue Sep 7, 2017 · 1 comment
Closed

Add "No to All" option for Resolve Missing Imports dialog #707

marco-brandizi opened this issue Sep 7, 2017 · 1 comment
Assignees
@matthewhorridge
Labels
Type: Enhancement A request for a change that is an enhancement
Milestone
Protégé 5.6.0

Comments

@marco-brandizi
Copy link

marco-brandizi commented Sep 7, 2017 •
edited
Loading

I have an ontology full of owl:imports statements, pointing at non-resolvale URIs. This causes Protegé to ask it a lot of times (one per URI) if I want to resolve the URIs (ie, specify which files they correspond to). Well, I don't want, and I'd like to tell it only once, with some additional button (or checkbox) like 'No to All'.
@matthewhorridge matthewhorridge added the Type: Enhancement A request for a change that is an enhancement label Jan 15, 2019
@matthewhorridge matthewhorridge added this to the Protégé 5.6.0 milestone Jan 15, 2019
@matthewhorridge matthewhorridge self-assigned this Jan 15, 2019
@matthewhorridge
Copy link
Contributor

👍

matthewhorridge added a commit that referenced this issue Apr 11, 2019
@matthewhorridge
Implements #707
605a3df
@matthewhorridge matthewhorridge changed the title Default answer for import resolution dialog. Add "No to All" option for Resolve Missing Imports dialog Apr 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@matthewhorridge matthewhorridge

Labels
Type: Enhancement A request for a change that is an enhancement
Projects
None yet
Milestone
Protégé 5.6.0
Development

No branches or pull requests
2 participants
@matthewhorridge @marco-brandizi