Opened 14 years ago

Closed 14 years ago

#5231 closed defect (fixed)

[DojoX] [FP] [PATCH] [CLA] Properly start-up and layout single layoutable child

Reported by: BlueFire Owned by: dante
Priority: high Milestone: 1.1
Component: Dojox Version: 1.0
Keywords: Cc:
Blocked By: Blocking:


It was not possible to add e.g. a TabContainer? to a FloatingPane? because the FP would never initiate an active resizing. The attached patch makes use of the provisions provided by FPs ancestor dojo.layout.ContentPane? to detect if the single child of the FP is a resizable widget. Resize-events are emitted to the child whenever the FP is resized. The area emitted to the child corresponds to the content area of the FP.

Also, in any case, during startup of the FP, an initial resize event is generated with the original position of the FP. This allows a potentially present child to initialize its size properly.

CLA on file: UPW Innovative IT-Lösungen GmbH

Attachments (1)

dojoFP-childLayout_20071124.patch (3.4 KB) - added by BlueFire 14 years ago.
FP child layout patch against rev 11621

Download all attachments as: .zip

Change History (4)

Changed 14 years ago by BlueFire

FP child layout patch against rev 11621

comment:1 Changed 14 years ago by BlueFire

  • Patch also updates the test case to include FP with nested TabContainers?
  • Removed left-over of the highlight code previously introduced by dante

comment:2 Changed 14 years ago by dante

Status: newassigned

comment:3 Changed 14 years ago by dante

Resolution: fixed
Status: assignedclosed

(In [11624]) fixes #5219 - destroy contents as well as pane on close. fixes #5231 - patch from BlueFire? allowing the child of a floatingpane to be a LayoutWidget? and size accordingly, and fixes #5232 - another patch from BlueFire? to make resize handle use a single 'rubberband' for virtual sizing.

Note: See TracTickets for help on using tickets.