File dialogue rule #351
Merged
File dialogue rule #351
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LexiconCode
added
New Feature
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements #348
Creates an app rule which identifies file dialogues by title and provides commands for navigating them. This method works in the programs I have tested it with.
To do:
test on more programsSeems to work in all standard save/open dialogues. Some programs have their own, but I'm not sure there is much that can be done about that beyond creating separate rules for each.add more potential file dialogue window names to the context - browse? open folder? open project?title finding seems to be fairly fuzzy, so "open" works for "open file" etcThink about whether grammar can be improveddocsThis is an excellent idea though. Wish I'd thought of it!