User forums > General (but related to Code::Blocks)

A feature request about CC and BrowseTracker

(1/8) > >>

ollydbg:
Hi, all.

Did you notice this issue:

When I just right click on an variable, then select "Find deceleration of XXX", then after see its type, I would just "jump back" to the original position.

Currently, what we can do is using the browsTracker plugin, I can hold the left mouse button before the jump, then if I want a jump back, I can press ALT+ left arrow button, even if we jump aross two files, we had to press "ALT + up arrow".

This is really annoying. I suggest the browseTracker could automatically record the caret position, so it can easily go backward and forward. (Note, if you have used Visual Assist plug of Visual C++, you're familiar with this behavior)

I just want any comment and objection of this feature request.

Thanks.

Pecan:

--- Quote from: ollydbg on July 29, 2009, 02:06:37 pm ---...
 even if we jump aross two files, we had to press "ALT + up arrow".

--- End quote ---

I don't understand what you're describing here. Could you give an example please.


--- Quote from: ollydbg on July 29, 2009, 02:06:37 pm ---This is really annoying. I suggest the browseTracker could automatically record the caret position, so it can easily go backward and forward. (Note, if you have used Visual Assist plug of Visual C++, you're familiar with this behavior)
...

--- End quote ---

I've never used visual Assist, so you'll have to describe the behavior and give an example.

ollydbg:
@pecan

Ok, I find the function description here:

http://www.wholetomato.com/products/features/navigate.asp

Which means the "editing position" can automatically saved, so, people can navigate easily.


--- Quote ---There is no way to control what Visual Assist X considers a location worth remembering. Generally speaking, Visual Assist X remembers files and lines visited. Small movements are ignored.

--- End quote ---

Edit:

People has request that feature. In

http://forums.codeblocks.org/index.php/topic,3082.msg24426.html#msg24426

http://forums.codeblocks.org/index.php/topic,5552.msg42953.html#msg42953

http://forums.codeblocks.org/index.php/topic,8057.0.html

paragraph 3 of this post:
http://forums.codeblocks.org/index.php/topic,3297.msg26000.html#msg26000

http://forums.codeblocks.org/index.php/topic,6093.msg72038.html#msg72038

Pecan:
On Alt-LeftArrow, BrowseTracker already jumps back to the editor cursor position the user had before activating another editor.

How do you see that as different from the "wholeTomato" descripton in your previous post?

On what user behavior or CB actions would you suggest BrowseTracker set a BrowseMark?

I am still not clear on how these requests are different from what BrowseTracker is now doing.

Maybe the best is for you to give and example, including the steps you would like to see BrowseTracker to follow.

ollydbg:
Ok, I will give a simple example.

For example you have a.cpp and b.cpp opened.

1, Now, you were editing in a.cpp, line 100.
2, you have jump( either jump from context menu->find implementation or you manually scroll down in the editor) to edit another position in a.cpp line 200.
3, After that, you would like to edit another position in b.cpp line 50, so, you were at b.cpp line 50.

Note: in visual assist, all the edit position will be recorded sequentially. So, it automatically keep a position stack like this:

......
a.cpp line 100
a.cpp line 200
b.cpp line 50

So, you can use "ALT + left arrow " to go backward, or "ALT + right arrow" to go forward.


In the current BrowseTracker, only the position you hold the left button mouse for 300ms will be recorded, so, My suggestion is: All the edit position should be automatically recorded.

I hope you can understand this feature request. In fact, this feature not only exists in programming IDEs, you can see this feature in Firefox or any web browser. ( forward and back navigate between a web history). Also, if you have Acrobat reader, they also has same functionality when navigate in a PDF.

Thanks.




Navigation

[0] Message Index

[#] Next page

Go to full version