Community
Participate
Working Groups
3.4.0 See Bug 241384 for details. When you open a dialog in an AbstractHandler and then call HandlerUtil.getActivePart() you will get back null. If you do not have the dialog you will get it before. This is marked as blocking Bug 241384 but as there is a workaround this is normal priority.
I suspect that this is because the IEvaluationContext provided to anyone that asks will track the global application state until the next selection change. The MessageDialog spins its own dispatch loop, and so information is cleared from the IEvaluationContext available through the ExecutionEvent. It might be that the IEvaluationContext returned from getCurrentState() must be a snapshot. PW
Tod, so you are seeing this problem on WinXP too?
No it is Linux specific.
Egads, I just got hit by this on our RCP product (it sure hurts when you only start to notice this when doing tests on Linux when your daily work is on XP). Any 3.5 plans for this, Paul?
It seems PDE is also hit by this via bug 274289.
I just ran into this as well - I have a handler that sometimes needs to open a dialog. In cases where the dialog is opened, a later call to get the active part returns null; when the dialog doesn't need to open, then everything works fine. I'm also only seeing it on Linux - no problems on Windows
*** Bug 297383 has been marked as a duplicate of this bug. ***
*** Bug 321594 has been marked as a duplicate of this bug. ***
*** Bug 360928 has been marked as a duplicate of this bug. ***
Is this fixed in a newer version already?
I have the same issue here running Debian Linux (Stretch) and Eclipse Neon.1 in EasyShell plugin. It works at Windows. As this is not fixed, is there a workaround for this?
I've faced the same problem with Version: Oxygen.1a Release (4.7.1a) and Debian Buster (10). Is there a workaround? Thanks.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.