Hi Marcus, The subclassing warning is a generic one. Similar to the checkSubclass method in SWT widgets. Please subclass to fix your issue and consider sharing it if you think it is useful for others.
Cheers, Wim On Mon, 14 Mar 2022 at 15:44, Hoepfner, Marcus via platform-dev < platform-dev@eclipse.org> wrote: > Hi, > > > > 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 and a Composite for the body). > > > > Means, when using a MasterDetailsBlock in a view or dialog all the above > mentioned is created. And in view or dialog 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)? > > > > Thanks, Marcus > > > _______________________________________________ > platform-dev mailing list > platform-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev >
_______________________________________________ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
