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

Can drop down hint list of "Object Property Assertions" dialog be longer in width? #1242

Open
yasenstar opened this issue Nov 8, 2024 · 2 comments
Labels
Type: Enhancement A request for a change that is an enhancement

Comments

@yasenstar
Copy link

Hello,

I'm using Protege 5.6.4 for making one system ontologies to analyze the inter-dependenies, for many infrastructure elements, the names are in quite long common prefix while difference in the end of the name (e.g. server host name, port number or specific DB name).

When I want to type some common prefix strings then use "Ctrl+Space" to pop up the auto-complete hint list, the width of the list is too short leads to not able to distinguish the different individuals, see below screenshot:

image

I have to go to the individual and manually copy then past into the object property assertion dialog.

I hope there's one setting somewhere that can allow me to show the drop down hint list in longer width, does anyone can help to let me know? Or give me some alternative solution from your experience.

Thanks a lot,
Xiaoqi

@gouttegd gouttegd added the Type: Enhancement A request for a change that is an enhancement label Nov 8, 2024
@ykazakov
Copy link
Contributor

for many infrastructure elements, the names are in quite long common prefix while difference in the end of the name

Looks like a classical use case for owl prefixes. I think that if the common parts were defined as prefixes, they would not be (fully) displayed in the list.

But I agree that one could also implement the search to match anywhere in strings, not only from the beginning.

@yasenstar
Copy link
Author

Thanks @ykazakov , indeed, owl prefixes is one way when those are large common items in ontology, however, my case - one application / infrastructure modeling - does have variable classes so they're not so "common" but under every class I'd like to keep the full individual name, not extracting them to prefix.

But I agree that one could also implement the search to match anywhere in strings, not only from the beginning.

For the "match anywhere", I think using "*" in the beginning already can allow this kind of wild (anywhere) string matching, but still, displaying length is not enough.

Screenshot 2024-11-11 234600

Regards, Xiaoqi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement A request for a change that is an enhancement
Projects
None yet
Development

No branches or pull requests

3 participants