566072 – Tree Viewers are not refreshed when started from another Eclipse (target platform)

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

Bug 566072 - Tree Viewers are not refreshed when started from another Eclipse (target platform)

Summary: Tree Viewers are not refreshed when started from another Eclipse (target plat...

Status:	CLOSED DUPLICATE of bug 567132

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	SWT (show other bugs)
Version:	4.17
Hardware:	PC Mac OS X

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-SWT-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2020-08-14 04:53 EDT by Matthias Becker
Modified:	2020-10-29 14:45 EDT (History)
CC List:	2 users (show)

See Also:

Attachments
Scrrenshot showing the issue (262.04 KB, image/png) 2020-08-14 04:53 EDT, Matthias Becker	no flags	Details
View All 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 Matthias Becker

2020-08-14 04:53:45 EDT

Created attachment 283870 [details]
Scrrenshot showing the issue

I face some strange issues with our current DevIDE on macOS.
When I start the target platform tree viewers are not refreshed correctly. This looks then something like the attached screenshot
 

This is only an issue in the target platform. I can reproduce this even down to 4.15 (did not check older versions). But I don't have this issue that long (since some weeks). I think that it has something to do with a change in one of the last macOS updates. I am running macOS 10.15.6 (but did also have this in 10.15.5).

Can somebody else reproduce this? Or can not reproduce on older macOS versions?

And how can this display issue only happen when started from another eclipse? What's the differences here?

Comment 1 Lakshmi P Shanmugam

2020-10-29 14:45:11 EDT

This is fixed with Bug 567132.

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