Bug 43970

Summary:	[History View] Configure history view columns
Product:	[Eclipse Project] Platform	Reporter:	Dani Megert <daniel_megert>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P4	CC:	Szymon.Brandys
Version:	3.0	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Dani Megert

2003-10-01 04:46:03 EDT

I20030930

The new linked mode in the history view is terrific! Most of the time I'd like
to see who committed something and the comment. Unfortunately the author column
is at the end of the table which forces me to have a really wide history view.

It would be great if I could configure the column sequence and even better:
which columns I'd like to see.

The workaround is to resize some columns to almost 0 width.

Comment 1 Jean-Michel Lemieux

2003-10-01 13:53:49 EDT

Good idea, and I'm glad you enjoy the history view linking :)

Comment 2 Michael Valenta

2005-05-06 17:19:09 EDT

This bug has not been touched for 2 years. Closing as WONTFIX. Please reopen if 
you feel this is still an important issue.

Comment 3 Dani Megert

2005-05-08 16:05:39 EDT

This is still a valid request and a feature I'd like to see.

Comment 4 Dani Megert

2005-05-08 16:05:47 EDT

This is still a valid request and a feature I'd like to see.

Comment 5 Dani Megert

2005-05-08 16:07:36 EDT

Sorry for the duplicate comment, my mouse hand was too fast ;-)

Maybe this could be discussed with SWT: I'd like to see this (configure the
column sequence) feature on any table.

Comment 6 Michael Valenta

2005-05-09 09:21:01 EDT

There is currently no plan to address this item

Comment 7 Szymon Brandys

2008-09-29 11:41:24 EDT

Now is the time...

Comment 8 Dani Megert

2008-10-01 03:42:29 EDT

Just for the records: this is no longer an issue for me personally because I now have the History view as wide fast view.

Comment 9 Eclipse Webmaster

2019-09-06 16:08:32 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.