INTEGRATION: CWS pbrwuno (1.2.490); FILE MERGED 2006/03/07 09:57:08 fs 1.2.490.6: correct :getHelpId 2005/10/17 10:27:59 fs 1.2.490.5: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:04 fs 1.2.490.4: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:46 fs 1.2.490.3: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:03:31 fs 1.2.490.2: RESYNC: (1.2-1.3); FILE MERGED 2005/09/05 07:41:52 fs 1.2.490.1: #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.
INTEGRATION: CWS pbrwuno (1.2.490); FILE MERGED
2006/03/07 09:57:08 fs 1.2.490.6: correct :getHelpId
2005/10/17 10:27:59 fs 1.2.490.5: #i53095# make numeric field exchange its values as double
2005/10/17 07:17:04 fs 1.2.490.4: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:46 fs 1.2.490.3: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:03:31 fs 1.2.490.2: RESYNC: (1.2-1.3); FILE MERGED
2005/09/05 07:41:52 fs 1.2.490.1: #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.

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