Why does this keep appearing in the IDE?

[TerryRitchie]

Why does that back arrow keep appearing in the IDE offering to take me back to previous lines? (see picture below). What is it, what triggers it, and how do I stop it from appearing? Every now and then when I want to click on file I hit it instead.

Thanks.

[SMcNeill]

It's a "return to" arrow.    Say you're on line 110, then scroll and click on line 642.  Click the arrow, go back to line 110 when you finish your edit elsewhere.  No idea if it's optional, or not, ATM.

[FellippeHeitor]

Every jump to different sections of code makes the back arrow appear so you can go back to where you were before the jump.

The triggers are:
- Selecting a SUB/FUNCTION in the F2 dialog;
- Navigating through bookmarks with Alt+Up/Down arrows;
- Jumping to a line that had an error (either by clicking the link in the Status area or by using Ctrl+Shift+G).
- Jumping to a line (Search menu->Go to line or Ctrl+G)
- Jumping to a SUB/FUNCTION or a label by right-clicking a mention of it in the code and choosing->Go to...

There's no way to disable it in the current version, but it would be easy to add a toggle in the upcoming release.

[TerryRitchie]

Ok, gotcha. I pop around subs/functions a lot using F2 view so that's what's triggering it.

Yes, if possible an option to turn this off would be appreciated. I always try my hardest to use keyboard only shortcuts for everything when in the IDE but sometimes that pesky mouse use of mine gets in the way.

I'll make a change in code ... stare at it for a while ... decide that all is good in the world ... grab the mouse to click File-->Save.  But instead I send my code view somewhere else and all nirvana and concentration is broken in the land of good. :)

(I know, it's a minor annoyance. It's not a must have change by any means.)

Edit: One other quick change I would like is a change to the usage of CTRL-R to comment code. I use it a lot. It would really be great that if a section of code is already commented out, CTRL-R would remove the comments instead of adding a second set. Try as I might I just can't seem to remember CTRL-SHIFT-R and end up adding a second set of comments instead. CTRL-R would toggle comments on and off in other words.

[FellippeHeitor]

Edit: One other quick change I would like is a change to the usage of CTRL-R to comment code. I use it a lot. It would really be great that if a section of code is already commented out, CTRL-R would remove the comments instead of adding a second set. Try as I might I just can't seem to remember CTRL-SHIFT-R and end up adding a second set of comments instead. CTRL-R would toggle comments on and off in other words.

I think that instead of changing the current behavior of Ctrl+R and Ctrl+Shift+R we should have a new shortcut for a "Toggle comment" feature. I'm borrowing from Notepad++ here, which has add/remove and also toggle features. Their shortcut for toggling is Ctrl+Q.

Any thoughts/suggestions, Terry and everyone?

Edit: Maybe CTRL+T makes more sense.

[bplus]

Ha! I've been finding it handy now that I know about it.

[FellippeHeitor]

Ha! I've been finding it handy now that I know about it.

That's why I think we should add a new shortcut instead of changing the current usage, as people may have gotten used to them as they currently are.

[TerryRitchie]

Yes, toggling would work. I like that.