| Summary: | PlannerField: Split position between Table and ActivityMap | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Otmar Caduff <otmar.caduff> | ||||||
| Component: | Scout | Assignee: | Project Inbox <scout.core-inbox> | ||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | zimmermann | ||||||
| Version: | unspecified | Flags: | zimmermann:
indigo+
zimmermann: juno+ |
||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Otmar Caduff
Created attachment 207743 [details]
Screenshot displaying the problem.
Created attachment 207745 [details]
Proposed patch to be applied on 2011-june release
NEW - bug 365227: PlannerField: Split position between Table and ActivityMap https://bugs.eclipse.org/bugs/show_bug.cgi?id=365227 13.12.2011 dwi [contributed by Otmar Caduff - oca, BSI Business Systems Integration AG] Problem: Currently, there is no viable way to influence where the table is split from the activity map on a planner field. The problem arises especially when the table has more than one column to be shown. Currently, in org.eclipse.scout.rt.ui.swing.form.fields.plannerfield.SwingScoutPlannerField.initializeSwing(), the split is set statically to 168 pixels. Solution: Added method getConfiguredSplitterPosition() on org.eclipse.scout.rt.client.ui.form.fields.plannerfield.AbstractPlannerField, which returns 168 as per default and can be overriden by subclasses. org.eclipse.scout.rt.ui.swing.form.fields.plannerfield.SwingScoutPlannerField takes this property into account when creating the UI. Plug-Ins changed: org.eclipse.scout.rt.client, org.eclipse.scout.rt.ui.swing Migration: None shipped with eclipse scout 3.7.2 (indigo sr2) removed iplog flag from bug (the one on the patch is enough) |