Bug 572226 - invisible placeholder results in space still occupied
Summary: invisible placeholder results in space still occupied
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.20   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2021-03-23 12:25 EDT by Christoph Laeubrich CLA
Modified: 2021-05-13 06:28 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Laeubrich CLA 2021-03-23 12:25:58 EDT
I have a placeholder in a perspective. I remove the [ ] visible check.

When I start the application the placeholder part is not visible, but the placeholder itself still occupies space (I get a gray, empty area).

If I call "MPlaceholder#setVisible" from code, the part and the placeholder are hidden.
Comment 1 Rolf Theunissen CLA 2021-05-12 13:57:28 EDT
I am not able to reproduce this behavior. Could you provide an example project? Or (better) an JUnit test case? Or (what would be great) a gerrit to fix the issue ;)

Does the part have a (empty) toolbar? That might explain the issue, as toolbars are not well rendered when a part is not in a partstack. That is, they are rendered next to the part.
Comment 2 Christoph Laeubrich CLA 2021-05-13 01:51:41 EDT
If I remember right it should be reproducible this way:

Have a Sash with two parts each of them displayed by a placeholder:

|<Placeholder->Part A|<Placeholder->Part B|

I give both 500 as container data, now I start and see both parts with equal space.

The I remove [ ] visible check from second placeholder (that shows part B)

I start and see the first part and with equal space an empty area.
Comment 3 Rolf Theunissen CLA 2021-05-13 05:43:04 EDT
Still cannot reproduce, it is not efficient if we have to try to reproduce the corner case in which this occurs.
Please provide working reproductions for issues you find.
Comment 4 Christoph Laeubrich CLA 2021-05-13 06:28:22 EDT
Thanks for the patience. Sadly I'm not able to reproduce this in a simple application so this might caused by an invalid combination/usage and will close this as WORKSFORME as long as I can't find the root cause.