> - Is there a key mapping for going from the end brace to the first braces
> and vice versa? For example:
> void func() {
> //a long method
> }|
> Cursor is after the end brace. The tooltip shows the start brace for me
but
> I can't find a key map for moving to the start brace.
>
You have to be inside the block to be able to go to the beginning. Right now
you have to do Left to go inside the block then Ctrl-[.There has been several discussion on this. I agree with you. Most editors usually have a way from the caret just outside the } to go to the beginning. In addition the visual parenthesis matching is only displayed when the caret is just after the parenthesis. It is counter-intuitive not to be able go to the already highligthed matching parenthesis directly and have to go inside the block to do so. > - It would be VERY handy to see some lines of the code that appears in the > ctrl+Q tooltip. I need to do a "go to imlpementation" right now, which leads > me to losing the context I'm in. Ideally there should be a small button in > the ctrl+q tooltip, if I press it the toltip enlarges and shows the the > first 5 lines of the code, below that 5 lines another button can move me to > the implementation. +0.5. However you can quickly "drill down" by Ctrl-B/Ctrl-LeftClick to see the called method code than quickly go back with Ctrl-Alt-Left to go back. It is one of the most useful function while browsing the code IMHO. It will be even better when they implement vertical split. One could envision a mode where the drill down occurs in another split to keep the context > - There's a change method signature feature but no change variable > signature. If I change the type of a field, the get/set should also return > the new type. If I change the return of the getter the setter and the field > type should change accordingly. +1 > - If I change the exception type of a method, or the signature or ... and it > leads to problems in OTHER classes, there should be an option to check other > classes for errors caused by a change in this class. If I refactored it it > would be ok, but sometimes refactoring is not enough, say when I delete a > method or do a massive change. I don't want to run Ant again just to find > the other classes having errors because of the change. +1 _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
