Cosmetics / Usability Bug? -- When using any of the "Go To" methods....

First let me preface this with I don't think this problem is EAP specific, it has been this way pretty much as long as I can remember, but since the 2.5 branch is probably frozen, I'll post this here for 3.0 or 3.5 inclusion:

When I start typing in a Go-To box (attached is Go To type by name), if I hit enter too quickly, the system will choose the wrong type. I.E. I type QCDAO, and theres a QuestionCell class and a QuestionControllerDAO, it will choose QuestionCell instead of the intended QCDAO.

(See attached pic for a snapshot mid-search -- If I hit enter here, I would get QuestionCell, not the desired QuestionControllerDAO)

Is there any way to allow the system to wait on the key command until after the list completes the lookup(like the way Console.ReadLine works)? I realize functionally it will be the same amount of time whether I wait or hit enter and wait, but it just seems more convenient (and accurate) to finish the search based on the term provided, not based on what the engine has time to keep up with by the time I hit ]]>.

I hope that request / question is clear?

Does anyone else have this problem, or is my PC just too slow and I have too many classes?

Thanks



Attachment(s):
QCQuickDraw.PNG
6 comments
Comment actions Permalink

Hello,

We specifially addressed this scenario in 2.5, and surely it is expected
to work in the desired fashion in the 3.0 release — that is, when you hit
the Enter key, first the items calculation is completed, and only then the
selected item gets executed.

There was a week-or-two-long degradation in the EAP/Beta stage of both the
2.5 and 3.0 versions due to the maintainance performed on the subsystem,
during which the Enter would apply to the incomplete list, but this won't
get into the release. You should definitely see Beta 2 which features the
fixed Enter in the Goto By Name dialogs family!


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

Serge,

I thought it wasn't fixed, my B for not verifying before posting... the problem experienced does not present in the latest nightly. Thanks for all your hard work on making this release the best yet!

Chad

Hello,

We specifially addressed this scenario in 2.5, and
surely it is expected
to work in the desired fashion in the 3.0 release ?
that is, when you hit
the Enter key, first the items calculation is
completed, and only then the
selected item gets executed.

There was a week-or-two-long degradation in the
EAP/Beta stage of both the
2.5 and 3.0 versions due to the maintainance
performed on the subsystem,
during which the Enter would apply to the incomplete
list, but this won't
get into the release. You should definitely see Beta
2 which features the
fixed Enter in the Goto By Name dialogs family!

?
Serge Baltic
JetBrains, Inc ? http://www.jetbrains.com
?Develop with pleasure!?

>

0
Comment actions Permalink

Hello,

The example given here was produced on 3.0.458.2. Now while
admittedly it isn't the latest nightly, it is post beta 2, and the
problem still exists, at least for me.

I am going to install the latest nightly and try again.


I'm afraid I cannot reproduce the reported behavior. Would you please create
a sample solution with the classes on which the error can be clearly illustrated,
and describe the exact steps to demonstrate the behavior? It's not that your
first description is unclear, but rather that I'd like to be sure I'm trying
to reproduce the right issue, because the one that seems to be the case has
recently been fixed …


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

Sorry, I went back and edited my post, but it didn't seem to make it into the newsgroups version. I could not reproduce the behavior either, so it apparently was an anomaly. Sorry for the wild goose chase.

Chadwick

0
Comment actions Permalink

Hello,

Sorry, I went back and edited my post, but it didn't seem to make it
into the newsgroups version. I could not reproduce the behavior
either, so it apparently was an anomaly. Sorry for the wild goose
chase.


Actually, we've been further investigating the issue on our side and finally
discovered a possibility for the behavior you reported. It involves typing
not too fast, but not too slow also ;) That is a conscequence of the new
non-blocking results list calculation feature (especially helpful when using
the new Goto Symbol). There are no chances to fix it in this release because
of the required architectural changes. Nevertheless, we're planning to implement
the full fix as soon as possible.

So, the summary: if you hit Enter within a one thirdth of a second afther
the last character typed, everything will be OK.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

Wow I really thought I was just going crazy. I'll try to make sure to either type too fast or too slow in the future ;)

Thanks for the help... the 3.0 release is really shaping up nicely.

Ciao

0

Please sign in to leave a comment.