INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into   the control for property A, which causes property B to be committed,   which causes the UI for property A to be rebuilt, then this will   crash currently. Reason: rebuildPropertyUI now synchronously replaces   the VCL-Window of the rebuilt control, which is exactly the one   which is still in some MouseButtonDown-handler.   possible solutions:   - see if rebuiltPropertyUI can be obsoleted - handlers should be able     to just obtain the XPropertyControl from the PropertyUI, and     re-initialize the control. Shouldn't they?`   - make one of the steps in the chain (mouse-click, handler-call,     rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties   (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work,   thus the browse buttons mostly do not work
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED
2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods
2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks
2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends
2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string >
2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double
2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED
2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
  the control for property A, which causes property B to be committed,
  which causes the UI for property A to be rebuilt, then this will
  crash currently. Reason: rebuildPropertyUI now synchronously replaces
  the VCL-Window of the rebuilt control, which is exactly the one
  which is still in some MouseButtonDown-handler.
  possible solutions:
  - see if rebuiltPropertyUI can be obsoleted - handlers should be able
    to just obtain the XPropertyControl from the PropertyUI, and
    re-initialize the control. Shouldn't they?`
  - make one of the steps in the chain (mouse-click, handler-call,
    rebuildPropertyUI-callback) asynchronous.
2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
  (not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
  thus the browse buttons mostly do not work

JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core,JurassicWordExcel/core