Expression Evaluation

"Franklin" <farj@bol.com.br> wrote in message news:csmfbi$gja$1@is.intellij.net...

Hi,

>

I remember, in Irida 3144, when we showed "Expression Evaluation" dialog, it automatically evaluated the selected expression (or
the word at the caret) without we having to press "Evaluate" button. In 3177, it's not doing that automatically.

>

Is this configurable? Where? If not, is this a bug or the common behavior?

>

Thanks,

>

Franklin.

This is by design.
Very often you need to change the expression that is pre-selected in the dialog, so automatic evaluation will only harm.
The behaviour you mention was an experiment which confirmed this, so we reverted it back. If expression in the text field is
complete, just hit Enter to evaluate it.

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"



"Franklin" <farj@bol.com.br> wrote in message news:csmfbi$gja$1@is.intellij.net...

Hi,

>

I remember, in Irida 3144, when we showed "Expression Evaluation" dialog, it automatically evaluated the selected expression (or
the word at the caret) without we having to press "Evaluate" button. In 3177, it's not doing that automatically.

>

Is this configurable? Where? If not, is this a bug or the common behavior?

>

Thanks,

>

Franklin.

That's too bad. All of us here liked it.

Norris Shelton
Sun Certified Java Programmer




Eugene Zhuravlev (JetBrains) wrote:

>This is by design.
>Very often you need to change the expression that is pre-selected in the dialog, so automatic evaluation will only harm.
>The behaviour you mention was an experiment which confirmed this, so we reverted it back. If expression in the text field is
>complete, just hit Enter to evaluate it.
>

>

If I need to evaluate an expression that's not in the code, I leave the
caret in a blank space and show the dialog, then I type the expression
and evaluate. However, very often, the expression I want to evaluate is
already in the code and, of course, after evaluating the expression, if
I want to evaluate something else, I change and press the evaluate button.

Should we create a feature request in the tracker and see how many votes
we'll get?

Franklin.

Eugene Zhuravlev (JetBrains) wrote:

This is by design.
Very often you need to change the expression that is pre-selected in the dialog, so automatic evaluation will only harm.
The behaviour you mention was an experiment which confirmed this, so we reverted it back. If expression in the text field is
complete, just hit Enter to evaluate it.

You won't get any vote from me. I'm quite happy that the expression is
preset to the current selection, but having the possibility to modify it
before it is executed is something I did't want to miss.

Franklin wrote:

If I need to evaluate an expression that's not in the code, I leave the
caret in a blank space and show the dialog, then I type the expression
and evaluate. However, very often, the expression I want to evaluate is
already in the code and, of course, after evaluating the expression, if
I want to evaluate something else, I change and press the evaluate button.

Should we create a feature request in the tracker and see how many votes
we'll get?

Franklin.

Eugene Zhuravlev (JetBrains) wrote:

>> This is by design.
>> Very often you need to change the expression that is pre-selected in
>> the dialog, so automatic evaluation will only harm.
>> The behaviour you mention was an experiment which confirmed this, so
>> we reverted it back. If expression in the text field is complete, just
>> hit Enter to evaluate it.
>>

--
Martin Fuhrer
Fuhrer Engineering AG
http://www.fuhrer.com

I agree with Martin, it's not a big deal to hit Enter if the expression is complete, but evaluating it automatically when it is not
in desirable state may have very undesirable effects on debugged application.

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"