Can someone explain the Back/Forward algorithm?

Hi,

I have a lot of trouble predicting where Back (ctrl+alt+left) and Forward (ctrl+alt+right) are going to take me a lot of the time.  Let me present a test to you:

I've got 3 tabs open for 3 classes: A, B, C.  On A, I click somewhere in the editor.  Then I go to B and click somewhere.  Then I go to C and cllick somewhere.

From C, if I were to go Back twice, here's what I would EXPECT to happen: It would jump to where I clicked on B, then it would jump to where I clicked on A.

This doesn't happen at all.  In fact, to me it's totally unpredictable.  Often, unrelated classes like D and F get opened which had nothing to do with where I was 30 seconds ago.

Let me try this again only this time I press space after I click.  Here's what I'd expect to happen: It would jump to where I pressed space on B, then it would jump to where I pressed space on A.

Again, this doesn't happen at all.  It also opens up class D and F.  For me, going forward is just as unpredictable.  I'd love to know how this functionality works.  As a note, I'd prefer it to work the way I expect.  I'd think that most people would agree with me (but I'm biased ).

Thanks

9 comments
Comment actions Permalink

Yeah, I don't get it either, it doesn't make any sense.  I still use forward/back and wind up in places that I don't remember being in.  I do remember this working better in previous releases (maybe back in the 4/5 days).

0
Comment actions Permalink

It may be this known issue: http://www.jetbrains.net/jira/browse/IDEADEV-32713
The fix was not ported back to 8.1.

Alexander.

0
Comment actions Permalink

Actually navigation history is fundamentally broken in IntelliJ 8. Build 9013 worked fine, all builds after that have been broken (including released versions).

See:

http://www.jetbrains.net/jira/browse/IDEA-20496

It seems like Jetbrains has totally forgotton about this one.

Navigation history jumps to files not even in the current project and there is no pattern to files that are jumped to.

All my co-workers who have tried IntelliJ 8.x have the same problem. To make matters worse "downgrading" to IntelliJ 7.x doesn't help. If you do 7.x has the same problem.

IntelliJ 8.x has broken navigation history.

I have done a totally fresh install on a new machine and the same problem occurs.

0
Comment actions Permalink

Michael Parmeley wrote:

Actually navigation history is fundamentally broken in IntelliJ 8. Build 9013 worked fine, all builds after that have been broken (including released versions).

See:

http://www.jetbrains.net/jira/browse/IDEA-20496

It seems like Jetbrains has totally forgotton about this one.

Navigation history jumps to files not even in the current project and there is no pattern to files that are jumped to.

IntelliJ 8.x has broken navigation history.


... and god help you if you only have a single tab open at any one time
- then even if the navigation history works ok, the caret isn't in the
place you left it when you switch between files :(
http://www.jetbrains.net/jira/browse/IDEADEV-31082
Looks like this is to be fixed for Maia, but I can't believe this has
been broken throughout a whole version of IDEA 8, 8.1 and 8.1.1 :-S
N.

0
Comment actions Permalink

On Sun, 12 Apr 2009 15:24:58 +0100, Nathan Brown wrote:

Michael Parmeley wrote:

>> Actually navigation history is fundamentally broken in IntelliJ 8.

>> It seems like Jetbrains has totally forgotton about this one.

... and god help you if you only have a single tab open at any one time


Hey, never mind - at least we now have a nice shadow effect on the
foreground tasks dialog. Who needs a working IDE when there's a Wow!
factor available?

--
Mark Scott
mark@codebrewer.com

0
Comment actions Permalink

Hello Mark,

>>> Actually navigation history is fundamentally broken in IntelliJ 8.
>>>
>>> It seems like Jetbrains has totally forgotton about this one.
>>>
>> ... and god help you if you only have a single tab open at any one
>> time
>>

Hey, never mind - at least we now have a nice shadow effect on the
foreground tasks dialog. Who needs a working IDE when there's a Wow!
factor available?


Actually the point of changes to the foreground tasks dialog was not to add
any Wow! factor, but rather to solve the long-complained-about focus stealing
problems (the progress dialog is now not a dialog at all but rather painted
via a GlassPane, so it doesn't affect the focus in any way). Adding the shadow
was just a side effect of the rewrite.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hi Dmitry,

On Mon, 13 Apr 2009 09:17:49 +0000, Dmitry Jemerov wrote:

>> Hey, never mind - at least we now have a nice shadow effect on the
>> foreground tasks dialog. Who needs a working IDE when there's a Wow!
>> factor available?


Actually the point of changes to the foreground tasks dialog was not to
add any Wow! factor, but rather to solve the long-complained-about focus
stealing problems (the progress dialog is now not a dialog at all but
rather painted via a GlassPane, so it doesn't affect the focus in any
way). Adding the shadow was just a side effect of the rewrite.


I posted in haste and wasn't exactly constructive in my criticism so I
apologise. I'm sure cosmetic changes like the shadow effect are indeed
side-effects of other work, added with little effort.

--
Mark Scott
mark@codebrewer.com

0
Comment actions Permalink

Dmitry Jemerov wrote:

Actually the point of changes to the foreground tasks dialog was not to
add any Wow! factor, but rather to solve the long-complained-about focus
stealing problems (the progress dialog is now not a dialog at all but
rather painted via a GlassPane, so it doesn't affect the focus in any
way). Adding the shadow was just a side effect of the rewrite.

Hi Dmitry,
Given this now is the case, is there a reason that progress dialogs
still block other project frames? For instance, I'm just opening
another project, and have got the dreaded "Parsing Files" dialog up, but
I cannot continue working on the project I already have open whilst this
parsing is being done, even though the parsing has nothing to do with
the original project.
N.

0
Comment actions Permalink

That is possibly IDEA-22870 issue which is staying opened for more than year.
Now IDEA 9.0.3 has been released, but the issue hasn't closed yet.

See topic at http://devnet.jetbrains.net/message/5268504

0

Please sign in to leave a comment.