AutomationPeer editor extension #332
No reviewers
Labels
No labels
Area-Accessibility
Area-Build
Area-CodeCompletion
Area-Document
Area-Documentation
Area-Editing
Area-Folding
Area-Highlighting
Area-i18n
Area-Indentation
Area-NetFx
Area-Rendering
Area-Search
Area-Snippets
dependencies
duplicate
Feedback Needed
help wanted
invalid
Issue-Bug
Issue-Discussion
Issue-Enhancement
Issue-Performance
Issue-Question
on-hold
Resolution-Answered
Resolution-By Design
Resolution-Duplicate
Resolution-Fixed
Resolution-Won't Fix
Up-for-Grabs
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-icsharpcode/AvalonEdit!332
Loading…
Reference in a new issue
No description provided.
Delete branch "sloutsky/automationpeer-editor-extension"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add extension to text editor that allows to inject automation peer that represents IntelliSense suggestion list and the currently selected suggestion - to allow screen narrators to read the suggestion.
Thank you very much for your pull request! The changes are looking good, just a few remarks:
If you don't have time to apply these changes, I can do that for you once we merge this.
I will have to take a closer look and test how Narrator behaves now.
I have renamed the property. Now I need to figure how to get rid of the "bad commits"
I normally use the
gitkUI tool for this as it's more convenient and you don't have to remember commit hashes. Also the command-line instructions might not use the minimal amount of commands.Assuming you are on the correct branch:
use
git logto find the commit hashes of all the commits you want to keep.If you want to merge the "Renaming property name" commit and the first commit into one, you can use steps in 4, otherwise just skip those.
git reset --hard origin/masterresets everything to the original state (this is a destructive action for all code that is not committed!)git pull --rebase https://github.com/icsharpcode/AvalonEdit.git mastergets the latest code from our repo (if your origin/master already has the latest revision, you can omit this)git cherry-pick <commit-hash>for every commit you want to addHEADpoints tocommit-hash1now):git cherry-pick <commit-hash2>git reset --mixed <commit-hash1>git commit --amendgit push --forceto reset the pull request branch and remove the unwanted commits.Hope this helps!
Looks like this didn't work out as expected. If you want, I can just clean it up manually before merge.
Yep, indeed - it looks I've messed this up. If you can handle this upon merge - this would be great!
Hmmm, it seems, this change currently does not provide a out-of-the-box solution for users of AvalonEdit. I would have expected Narrator to properly work out-of-the-box with how we currently use/instantiate the
CompletionWindowin the sample application:github.com/icsharpcode/AvalonEdit@395ef81668/ICSharpCode.AvalonEdit.Sample/Window1.xaml.cs (L124-L154)Seems like I will have to dig around to get this to work properly like in VS. Thanks anyway for the starting point.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.