Community
Participate
Working Groups
create a try block without a catch or finally. There is no squiggly underline on the closing brace, so the error is not easily accessible using F2. Type "; ff" in a method body somewhere. There *IS* a squiggly underline under the semicolor, but F2 fails there too.
This works for me using 3.2 RC7 and latest 3.3 build (I20060620-1010). Note: F2 applies if the caret is before or inside the word with the error but not if the caret is just after the word. This counts to the next word/error. It also applies if the full word/error is selected.
I tried F2 on both sides of the character that was underlined. Could you reproduce in RC5, or do you know which bug fixed after RC5 addressed this issue? Thanks.
Sorry but I don't have time to go back in time ;-) and we don't patch RC5 either. I tried latest 3.2 and 3.3 builds. Maybe it's something special with the error annotation? Please try one of the latest build and if you still see it provide more detailed steps to reproduce the problem.
Reproduced in Fresh RC7 workspace: public class Foo { public static void main(String[] args) { try { System.out.println(""); } } }
I could not get F2 to work for this either: public class Foo { public static void main(String[] args) { try { System.out.println("); } } }
See ;-) Me neither. It's not only F2, also the hovers aren't showing for me in that example.
Similar problem using 3.1.x but there at least the hover works i.e. one can use hover + F2. Might be a good 3.2.1 candidate if the fix is simple.
The F2 problem which was already in 3.1 is caused by the fact that the information provider is only registered for some content types (partitions). Hence in things like String partitions it doesn't work. ==> fixed by using the same content types as the hovers i.e. all configured content types. The hover stopped working due to fixing bug 94705 where we made the Word Finder more strict. Fixed this one too. Fixed in HEAD and released into R3_2_maintenance.
verified in M20060830-0800
