Community
Participate
Working Groups
In the Display view if you have to evaluate an expression (e.g. A.foo()) the following steps are needed - Type 'A.foo()' - Select 'A.foo()' - Inspect Can we reduce the number of steps ? For example by making Inspect command work to on the expression on the current line even if there is no selection, so that the following steps are needed - Type 'A.foo()' - Press Ctrl+Shift+I (Inspect)
(In reply to comment #0) > In the Display view if you have to evaluate an expression (e.g. A.foo()) the > following steps are needed > - Type 'A.foo()' > - Select 'A.foo()' > - Inspect > > Can we reduce the number of steps ? For example by making Inspect command work > to on the expression on the current line even if there is no selection, so that > the following steps are needed > - Type 'A.foo()' > - Press Ctrl+Shift+I (Inspect) -1. I think this would be misleading. The only thing I could imagine is to use the caret location and then use/evaluate whet F3 would open, e.g. if the caret is inside "foo" it would evalate A.foo().
(In reply to comment #1) > -1. I think this would be misleading. The only thing I could imagine is to use > the caret location and then use/evaluate whet F3 would open, e.g. if the caret > is inside "foo" it would evalate A.foo(). This would also work for me.
I have to agree with Dani on this one, it would be confusing to understand what is being inspected in the empty selection case. I do like the carat location idea though.
I assume the caret location idea will be applied to the Java Editor as well and not just to display view.
(In reply to comment #4) > I assume the caret location idea will be applied to the Java Editor as well and > not just to display view. This already exists in the java editor. If the caret is inside of a variable or method and Inspect or Display is run, the containing member will be inspected. The only limitation I currently see is when the caret is at the end of the line (before or after a semicolon) the inspect does not find the previous member.