-
Notifications
You must be signed in to change notification settings - Fork 155
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
Handle the case when application has no focus in ApplicationPartService #1890
base: master
Are you sure you want to change the base?
Conversation
Test Results0 tests 0 ✅ 0s ⏱️ Results for commit 97cdf28. ♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@laeubi thank you for contributing this. I only have a minor concern regarding the changes in the test class.
NOTE: I only skimmed through the the other changes but I haven't tested them. I could test them do it if you briefly describe how to do it.
....eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/dialogs/UIWorkingSetWizardsAuto.java
Outdated
Show resolved
Hide resolved
89047b5
to
e8eeb57
Compare
Unrelated changes were moved to another PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks better. I'm still missing a brief "How to test" in this PR and a description of the original bug/behavior that caused this PR.
Sadly the case is quite tricky to test, you need a custom RCP application, you need an external trigger (e.g. Network communication) ... |
Currently when the application has no focus there is also no active window child and in this case several actions still fail even though a part is available for perform actions. This now handles the case of an application without focus with an empty optional to allow fall back to the part context. If that context has still no suitable part service implementation as a last resort the containing window context is used.
e8eeb57
to
97cdf28
Compare
Currently when the application has no focus there is also no active window child and in this case several actions still fail even though a part is available for perform actions.
This now handles the case of an application without focus with an empty optional to allow fall back to the part context. If that context has still no suitable part service implementation as a last resort the containing window context is used.