-
Notifications
You must be signed in to change notification settings - Fork 114
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
Present plugins matching selected extension in Open file as type pull down #19884
Comments
I was talking about the interface controlling this with @brugger1 and he suggested some improvements and we observed some oddities about this interface...
|
Yes, I am aware of that. But, in my experience on macOS, its not really an auto-complete per se. I mean, if I hit the |
In any event, auto-completion behavior is somewhat orthogonal to the feature request here. It should just recognize the file type I have selected and pull up the correct options without the user having to do extra work to get them. |
Sure, I just wanted to mention it to raise awareness to a quick way to get db types. |
Is your feature request related to a problem?
We have a lot of database plugins. When opening a file, say a MOAB file with a
.h5m
extension, its a real pain to scroll through the list of them to find MOAB and select it.When file(s) are selected (highlited via a mouse gesture) in the
Files:
list, I would like for VisIt to present theOpen file as type
pull down in two segments. First, listing all the plugins that match all the extension(s) in the set ofFiles
that have been selected followed by some kind of a seperator line (maybe just a blank entry) and then the full alphabetical list of plugins.Next, if a plugin does NOT have any options defined, it should not be listed or it should not be listed among the plugins that DO have options defined.
That way, if I select a
.h5m
file in theFiles
list, when I go to the pulldown,MOAB
will appear as an option at the top. Likewise for other formats with relatively unique extensions (e.g.silo
,root
, etc.).The text was updated successfully, but these errors were encountered: