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

Bug 171891

Summary:	[Markers] Problems view column width wrong when update from 3.1
Product:	[Eclipse Project] Platform	Reporter:	Walter Harley <eclipse>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	bigguy
Version:	3.3	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Walter Harley

2007-01-26 19:32:14 EST

Create a workspace in Eclipse 3.1.2, that contains a file with a problem (e.g. a Java syntax error).  Exit Eclipse and then load the workspace in Eclipse 3.2 or 3.3 (I am testing on 3.3M4).

The first column in the 3.1 problems view has no title and just contains an icon; there is a separate description column.  Because problems are shown hierarchically by default in 3.2+, the description column is now first, but it gets sized the same as the icon column, which is too narrow for any indented content to show.  The result is that the user sees a first line containing just a '-' icon, and a second line showing no description and no error icon, just resource, path, and location.

Closing the problems view and reopening it causes it to resize properly.  Expected: this workaround to be unnecessary.

Duplicate, maybe?  All the similar bugs I found were either "works for me" or "fixed", which this is not; I didn't see anything that explicitly called out the upgrade scenario, so maybe this is the missing piece of information everyone's been waiting for :-)

FWIW, it's not just a nit: when customers of our Eclipse-based product upgrade versions they also get a new version of Eclipse.  We are seeing cases where our upgrade process introduces build errors, but the users don't notice the errors because there's no description or error icon showing; confusion ensues.

Comment 1 Wojtek Bok

2008-11-05 13:59:59 EST

I am not sure if this is related, but the problem view does not always persist the column widths.

I set the column widths, then shutdown Eclipse. The next day I start Eclipse and about half the time the column widths revert to the default settings. The other half of the time they retain the widths I set. I cannot find a pattern to this behaviour.

However the changed column order is persisted.

I am using 3.4

Comment 2 Walter Harley

2008-11-05 14:18:06 EST

Wojtek, is there any possibility that you are accessing the same workspace from multiple Eclipse versions?

Also, was the workspace created with the same Eclipse version that you are using now?

If this workspace is only being touched by one version of Eclipse, then I do not think this bug is related, and you should report it separately, making sure to specify what platform (Mac, Windows, Linux) you are running on.  You should also check in your error log (Error Log view) to see if perhaps some plug-in is reporting problems.

Comment 3 Wojtek Bok

2008-11-05 14:57:28 EST

I am only using 3.4 from a single machine. The workspace is on the local drive

The workspace was created with version 2.x (a long time ago), and each subsequent version is pointed to the same workspace.

I will open a new bug with the log snippet. Ok, Bug 253980.

Comment 4 Susan McCourt

2009-07-09 19:18:47 EDT

As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009

Comment 5 Eclipse Webmaster

2019-09-06 16:12:59 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.

Comment 6 Eclipse Genie

2021-09-07 12:37:27 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.