Community
Participate
Working Groups
I20090304-0834 Java compare editor: NLS hover and hyperlink only work if another Java editor on the same file is already open. That's rather unpredictable. I was very confused when I was in a debug session, the default hover for an NLS field was the variable value hover, and when I pressed my 'Externalized String' hover modifier key, the NLS hover only appeared in some files.
> hyperlink Tomasz pointed out that Ctrl+click actually works. What doesn't work for links is the hyperlink target popup ("Open in 'XX.properties'" / "Open Declaration"): The popup doesn't appear unless another Java editor is open on the file.
Tomasz, do you have time to look into this?
Sure, would 3.5 M7 be ok with you?
Sure.
NLSKeyHyperlinkDetector.detectHyperlinks() returns null for an embedded text viewer from the Compare Editor. This is caused by the fact that SharedASTProvider.getAST(...) call in line 64 returns non-null CompilationUnit only when another Java editor is open on the file.
Passing WAIT_YES as wait flag to SharedASTProvider.getAST(...) the hyperlink target popup reappears with the missing "Open in '<bundle>.properties'". This is not a solution, it only proves that Java Compare does not provide AST on its own, it needs to have another CU editor open to work properly.
We should not start to mess with ASTs at this stage. Please target early 3.6.
Dani, isn't this one blocked by bug 273454 or bug 273455 you have filed recently?
>Dani, isn't this one blocked by bug 273454 or bug 273455 you have filed >recently? bug 273454 yes, bug 273455 no
Guys, given the fact that this bug is blocked by bug 273454 which has no Target Milestone set, do you think it would be OK to remove the target here? I don't want to sound like I'm pushing you into fixing it, the truth is that most probably I won't be able to fix this bug in 3.6.
>OK to remove the target here Done.
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.