546113 – going back from "open declaration"

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 546113 - going back from "open declaration"

Summary: going back from "open declaration"

Status:	CLOSED DUPLICATE of bug 413505

Alias:	None

Product:	CDT
Classification:	Tools
Component:	cdt-parser (show other bugs)
Version:	4.0.3
Hardware:	PC Linux

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Project Inbox
QA Contact:	Doug Schaefer

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2019-04-04 09:40 EDT by Marek Husar
Modified:	2019-04-04 16:50 EDT (History)
CC List:	4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Marek Husar

2019-04-04 09:40:11 EDT

Eclipse is a great product, really big thanks for that.
But I have some problem with action "Back", it makes me crazy :).

Action "Back" does not work correctly when going back from action "open declaration" in C/C++ code.
In C/C++ editor (.h, .cpp files), when cursor is on name of function and I press F3 ("open declaration"), given function will be opened. This behavior working like a charm. But then, when I press action "Back", the editor will switch me to the different place of file, no to the place, where I pressed F3. This problem is happening quite often, but no every time.

I noticed this behavior for a long time and it has happened in older versions as well.

Comment 1 Hannes Vogt

2019-04-04 16:01:04 EDT

I can confirm that I sometimes have the same problem. I tried to reproduce it in a simple project now, but didn't manage to. Would be nice if someone finds the steps to reproduce the issue.

Comment 2 Nathan Ridge

2019-04-04 16:50:59 EDT

I see this a lot too. It's a bug in the Eclipse Platform's navigation history feature, which is what powers the "Back" and "Forward" actions. ("Open Declaration" just uses that platform API to insert a new entry into the navigation history.)

*** This bug has been marked as a duplicate of bug 413505 ***