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

Parse errors during file open fail silently #29

Open
cbielow opened this issue Aug 11, 2022 · 0 comments
Open

Parse errors during file open fail silently #29

cbielow opened this issue Aug 11, 2022 · 0 comments

Comments

@cbielow
Copy link

cbielow commented Aug 11, 2022

When opening a file, which cannot be parsed (due to parse errors), see e.g. #28, Protege will simply not show anything in the user interface. It behaves as if the user did not try to open a file.
In reality, the log window shows a bunch of errors, but the user has to know that this log window exists, and open it manually to see what the problem was.
The UI should at least show a messagebox or (better) open the log window automatically if an error was encountered.

Tested with Protege 5.5.

Minimal example (save as bug.obo)

import: http://purl.obolibrary.org/obo/pato.obo

[Typedef]
id: has_regexp
name: has regexp

silently fails (until #28 is fixed at least) and does nothing in the UI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant