Bug 577459 - Usage of MasterDetailsBlock in view or dialog
Summary: Usage of MasterDetailsBlock in view or dialog
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.23   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-25 03:22 EST by Marcus Höpfner CLA
Modified: 2021-11-25 03:24 EST (History)
2 users (show)

See Also:

Attachments
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 Marcus Höpfner CLA 2021-11-25 03:22:38 EST 
o.e.ui.forms.MasterDetailsBlock requires a ManagedForm in createContent(IManagedForm managedForm).
ManagedForm wants (or creates) a ScrolledForm. A ScrolledForm creates a Form (with FormHeading head and Composite body).

Means, when using a MasterDetailsBlock in a view or dialog all the above mentioned is created. And in the UI I see a MasterDetailsBlock with white space above. This is the form heading.

Neither SrolledForm nor Form should be subclassed (according to java doc) to overwrite this handling.

Extending ManagedForm (just with a composite instead of ScrolledForm) seems uncommon as well. At least I didn't find an implementation.


What can be done to just use a MasterDetailsBlock in others than editors (e.g. views, dialogs, wizardpages)?