INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
/*************************************************************************
*
2008-04-11 09:51:50 +00:00
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER .
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
*
2008-04-11 09:51:50 +00:00
* Copyright 2008 by Sun Microsystems , Inc .
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
*
2008-04-11 09:51:50 +00:00
* OpenOffice . org - a multi - platform office productivity suite
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
*
2008-04-11 09:51:50 +00:00
* $ RCSfile : formcomponenthandler . cxx , v $
2008-06-16 11:42:41 +00:00
* $ Revision : 1.18 $
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
*
2008-04-11 09:51:50 +00:00
* This file is part of OpenOffice . org .
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
*
2008-04-11 09:51:50 +00:00
* OpenOffice . org is free software : you can redistribute it and / or modify
* it under the terms of the GNU Lesser General Public License version 3
* only , as published by the Free Software Foundation .
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
*
2008-04-11 09:51:50 +00:00
* OpenOffice . org is distributed in the hope that it will be useful ,
* but WITHOUT ANY WARRANTY ; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE . See the
* GNU Lesser General Public License version 3 for more details
* ( a copy is included in the LICENSE file that accompanied this code ) .
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
*
2008-04-11 09:51:50 +00:00
* You should have received a copy of the GNU Lesser General Public License
* version 3 along with OpenOffice . org . If not , see
* < http : //www.openoffice.org/license.html>
* for a copy of the LGPLv3 License .
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
*
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
2006-09-16 12:17:24 +00:00
// MARKER(update_precomp.py): autogen include statement, do not remove
# include "precompiled_extensions.hxx"
2008-12-16 13:30:53 +00:00
# include "controltype.hxx"
# include "extensio.hrc"
# include "fontdialog.hxx"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
# include "formcomponenthandler.hxx"
2008-12-16 13:30:53 +00:00
# include "formlinkdialog.hxx"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
# include "formmetadata.hxx"
# include "formresid.hrc"
2008-12-16 13:30:53 +00:00
# include "formstrings.hxx"
# include "handlerhelper.hxx"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
# include "listselectiondlg.hxx"
2008-12-16 13:30:53 +00:00
# include "pcrcommon.hxx"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
# include "selectlabeldialog.hxx"
# include "taborder.hxx"
2008-12-16 13:30:53 +00:00
# include "usercontrol.hxx"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
/** === begin UNO includes === **/
# include <com/sun/star/lang/NullPointerException.hpp>
# include <com/sun/star/awt/XControlModel.hpp>
# include <com/sun/star/lang/XServiceInfo.hpp>
# include <com/sun/star/form/FormComponentType.hpp>
# include <com/sun/star/beans/PropertyAttribute.hpp>
# include <com/sun/star/util/XNumberFormatsSupplier.hpp>
# include <com/sun/star/container/XNameAccess.hpp>
# include <com/sun/star/form/XForm.hpp>
# include <com/sun/star/container/XChild.hpp>
# include <com/sun/star/sdbc/XConnection.hpp>
# include <com/sun/star/sdb/CommandType.hpp>
# include <com/sun/star/form/XGridColumnFactory.hpp>
# include <com/sun/star/sdb/SQLContext.hpp>
# include <com/sun/star/sdbcx/XTablesSupplier.hpp>
# include <com/sun/star/sdb/XQueriesSupplier.hpp>
# include <com/sun/star/form/ListSourceType.hpp>
# include <com/sun/star/ui/dialogs/XExecutableDialog.hpp>
# include <com/sun/star/sdb/XSingleSelectQueryComposer.hpp>
# include <com/sun/star/ui/dialogs/XFilePickerControlAccess.hpp>
# include <com/sun/star/ui/dialogs/ExtendedFilePickerElementIds.hpp>
# include <com/sun/star/awt/XTabControllerModel.hpp>
# include <com/sun/star/form/FormSubmitEncoding.hpp>
# include <com/sun/star/awt/VisualEffect.hpp>
# include <com/sun/star/form/FormButtonType.hpp>
# include <com/sun/star/inspection/PropertyControlType.hpp>
# include <com/sun/star/util/MeasureUnit.hpp>
# include <com/sun/star/inspection/XObjectInspectorUI.hpp>
# include <com/sun/star/inspection/PropertyLineElement.hpp>
2007-01-02 14:53:53 +00:00
# include <com/sun/star/resource/XStringResourceManager.hpp>
2007-01-29 15:57:30 +00:00
# include <com/sun/star/resource/MissingResourceException.hpp>
2008-12-01 12:31:27 +00:00
# include <com/sun/star/graphic/GraphicObject.hpp>
2008-12-16 13:30:53 +00:00
# include <com/sun/star/text/WritingMode2.hpp>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
/** === end UNO includes === **/
2008-12-16 13:30:53 +00:00
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
# include <comphelper/extract.hxx>
2008-12-16 13:30:53 +00:00
# include <connectivity/dbconversion.hxx>
# include <connectivity/dbexception.hxx>
# include <cppuhelper/exc_hlp.hxx>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
# include <sfx2/app.hxx>
# include <sfx2/basedlgs.hxx>
# include <sfx2/docfilt.hxx>
2008-12-16 13:30:53 +00:00
# include <sfx2/filedlghelper.hxx>
# include <svtools/ctloptions.hxx>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
# include <svtools/colrdlg.hxx>
2008-12-16 13:30:53 +00:00
# include <svtools/filenotation.hxx>
# include <svtools/intitem.hxx>
# include <svtools/itemset.hxx>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
# include <svtools/moduleoptions.hxx>
2008-12-16 13:30:53 +00:00
# include <svtools/numuno.hxx>
# include <svtools/urihelper.hxx>
# include <svx/dialogs.hrc>
# include <svx/numinf.hxx>
# include <svx/svxdlg.hxx>
# include <svx/svxids.hrc>
# include <toolkit/helper/vclunohelper.hxx>
2007-05-10 09:47:38 +00:00
# include <tools/diagnose_ex.h>
2008-12-16 13:30:53 +00:00
# include <vcl/msgbox.hxx>
# include <vcl/stdtext.hxx>
# include <vcl/wrkwin.hxx>
2008-12-10 13:41:25 +00:00
# include <tools/StringListResource.hxx>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
# include <limits>
2008-12-01 12:31:27 +00:00
# define GRAPHOBJ_URLPREFIX "vnd.sun.star.GraphicObject:"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
//------------------------------------------------------------------------
extern " C " void SAL_CALL createRegistryInfo_FormComponentPropertyHandler ( )
{
: : pcr : : FormComponentPropertyHandler : : registerImplementation ( ) ;
}
//........................................................................
namespace pcr
{
//........................................................................
using namespace : : com : : sun : : star ;
2007-07-06 07:48:27 +00:00
using namespace uno ;
using namespace lang ;
using namespace beans ;
using namespace frame ;
using namespace script ;
using namespace form ;
using namespace util ;
using namespace awt ;
using namespace sdb ;
using namespace sdbc ;
using namespace sdbcx ;
using namespace form ;
using namespace container ;
using namespace ui : : dialogs ;
using namespace inspection ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
using namespace : : dbtools ;
2008-12-16 13:30:53 +00:00
namespace WritingMode2 = : : com : : sun : : star : : text : : WritingMode2 ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
//====================================================================
//= FormComponentPropertyHandler
//====================================================================
DBG_NAME ( FormComponentPropertyHandler )
2007-07-06 07:48:27 +00:00
# define PROPERTY_ID_ROWSET 1
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
//--------------------------------------------------------------------
FormComponentPropertyHandler : : FormComponentPropertyHandler ( const Reference < XComponentContext > & _rxContext )
: FormComponentPropertyHandler_Base ( _rxContext )
2007-07-06 07:48:27 +00:00
, : : comphelper : : OPropertyContainer ( FormComponentPropertyHandler_Base : : rBHelper )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
, m_sDefaultValueString ( String ( PcrRes ( RID_STR_STANDARD ) ) )
, m_eComponentClass ( eUnknown )
, m_bComponentIsSubForm ( false )
, m_bHaveListSource ( false )
, m_bHaveCommand ( false )
, m_nClassId ( 0 )
{
DBG_CTOR ( FormComponentPropertyHandler , NULL ) ;
2007-07-06 07:48:27 +00:00
registerProperty ( PROPERTY_ROWSET , PROPERTY_ID_ROWSET , 0 , & m_xRowSet , : : getCppuType ( & m_xRowSet ) ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
//--------------------------------------------------------------------
FormComponentPropertyHandler : : ~ FormComponentPropertyHandler ( )
{
DBG_DTOR ( FormComponentPropertyHandler , NULL ) ;
}
2007-07-06 07:48:27 +00:00
//--------------------------------------------------------------------
IMPLEMENT_FORWARD_XINTERFACE2 ( FormComponentPropertyHandler , FormComponentPropertyHandler_Base , : : comphelper : : OPropertyContainer )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
//--------------------------------------------------------------------
: : rtl : : OUString SAL_CALL FormComponentPropertyHandler : : getImplementationName_static ( ) throw ( RuntimeException )
{
return : : rtl : : OUString ( RTL_CONSTASCII_USTRINGPARAM ( " com.sun.star.comp.extensions.FormComponentPropertyHandler " ) ) ;
}
//--------------------------------------------------------------------
Sequence < : : rtl : : OUString > SAL_CALL FormComponentPropertyHandler : : getSupportedServiceNames_static ( ) throw ( RuntimeException )
{
Sequence < : : rtl : : OUString > aSupported ( 1 ) ;
aSupported [ 0 ] = : : rtl : : OUString ( RTL_CONSTASCII_USTRINGPARAM ( " com.sun.star.form.inspection.FormComponentPropertyHandler " ) ) ;
return aSupported ;
}
2007-01-02 14:53:53 +00:00
//============================================
// TODO: -> export from toolkit
struct LanguageDependentProp
{
const char * pPropName ;
sal_Int32 nPropNameLength ;
} ;
static LanguageDependentProp aLanguageDependentProp [ ] =
{
{ " Text " , 4 } ,
{ " Label " , 5 } ,
{ " Title " , 5 } ,
{ " HelpText " , 8 } ,
{ " CurrencySymbol " , 14 } ,
2007-01-29 15:57:30 +00:00
{ " StringItemList " , 14 } ,
2007-01-02 14:53:53 +00:00
{ 0 , 0 }
} ;
namespace
{
bool lcl_isLanguageDependentProperty ( : : rtl : : OUString aName )
{
bool bRet = false ;
LanguageDependentProp * pLangDepProp = aLanguageDependentProp ;
while ( pLangDepProp - > pPropName ! = 0 )
{
if ( aName . equalsAsciiL ( pLangDepProp - > pPropName , pLangDepProp - > nPropNameLength ) )
{
bRet = true ;
break ;
}
pLangDepProp + + ;
}
return bRet ;
}
Reference < resource : : XStringResourceResolver > lcl_getStringResourceResolverForProperty
( Reference < XPropertySet > _xComponent , const : : rtl : : OUString & _rPropertyName ,
const Any & _rPropertyValue )
{
Reference < resource : : XStringResourceResolver > xRet ;
2008-06-16 11:42:41 +00:00
const TypeClass eType = _rPropertyValue . getValueType ( ) . getTypeClass ( ) ;
if ( ( eType = = TypeClass_STRING | | eType = = TypeClass_SEQUENCE ) & &
lcl_isLanguageDependentProperty ( _rPropertyName ) )
2007-01-02 14:53:53 +00:00
{
2008-06-16 11:42:41 +00:00
static const : : rtl : : OUString s_sResourceResolverPropName ( RTL_CONSTASCII_USTRINGPARAM ( " ResourceResolver " ) ) ;
Reference < resource : : XStringResourceResolver > xStringResourceResolver ;
try
{
xStringResourceResolver . set ( _xComponent - > getPropertyValue ( s_sResourceResolverPropName ) , UNO_QUERY ) ;
if ( xStringResourceResolver . is ( ) & &
xStringResourceResolver - > getLocales ( ) . getLength ( ) > 0 )
{
xRet = xStringResourceResolver ;
}
}
catch ( UnknownPropertyException & )
{
// nii
}
2007-01-02 14:53:53 +00:00
}
return xRet ;
}
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
//--------------------------------------------------------------------
Any FormComponentPropertyHandler : : impl_getPropertyValue_throw ( const : : rtl : : OUString & _rPropertyName ) const
{
2008-06-16 11:42:41 +00:00
const PropertyId nPropId ( impl_getPropertyId_throw ( _rPropertyName ) ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
Any aPropertyValue ( m_xComponent - > getPropertyValue ( _rPropertyName ) ) ;
2007-01-02 14:53:53 +00:00
Reference < resource : : XStringResourceResolver > xStringResourceResolver
= lcl_getStringResourceResolverForProperty ( m_xComponent , _rPropertyName , aPropertyValue ) ;
if ( xStringResourceResolver . is ( ) )
{
2007-01-29 15:57:30 +00:00
TypeClass eType = aPropertyValue . getValueType ( ) . getTypeClass ( ) ;
if ( eType = = TypeClass_STRING )
{
: : rtl : : OUString aPropStr ;
aPropertyValue > > = aPropStr ;
if ( aPropStr . getLength ( ) > 1 )
{
: : rtl : : OUString aPureIdStr = aPropStr . copy ( 1 ) ;
if ( xStringResourceResolver - > hasEntryForId ( aPureIdStr ) )
{
: : rtl : : OUString aResourceStr = xStringResourceResolver - > resolveString ( aPureIdStr ) ;
aPropertyValue < < = aResourceStr ;
}
}
}
// StringItemList?
else if ( eType = = TypeClass_SEQUENCE )
2007-01-02 14:53:53 +00:00
{
2007-01-29 15:57:30 +00:00
Sequence < : : rtl : : OUString > aStrings ;
aPropertyValue > > = aStrings ;
const : : rtl : : OUString * pStrings = aStrings . getConstArray ( ) ;
sal_Int32 nCount = aStrings . getLength ( ) ;
Sequence < : : rtl : : OUString > aResolvedStrings ;
aResolvedStrings . realloc ( nCount ) ;
: : rtl : : OUString * pResolvedStrings = aResolvedStrings . getArray ( ) ;
try
2007-01-02 14:53:53 +00:00
{
2007-01-29 15:57:30 +00:00
for ( sal_Int32 i = 0 ; i < nCount ; + + i )
{
: : rtl : : OUString aIdStr = pStrings [ i ] ;
: : rtl : : OUString aPureIdStr = aIdStr . copy ( 1 ) ;
if ( xStringResourceResolver - > hasEntryForId ( aPureIdStr ) )
pResolvedStrings [ i ] = xStringResourceResolver - > resolveString ( aPureIdStr ) ;
else
pResolvedStrings [ i ] = aIdStr ;
}
2007-01-02 14:53:53 +00:00
}
2007-01-29 15:57:30 +00:00
catch ( resource : : MissingResourceException & )
{ }
aPropertyValue < < = aResolvedStrings ;
2007-01-02 14:53:53 +00:00
}
}
else
impl_normalizePropertyValue_nothrow ( aPropertyValue , nPropId ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
return aPropertyValue ;
}
//--------------------------------------------------------------------
Any SAL_CALL FormComponentPropertyHandler : : getPropertyValue ( const : : rtl : : OUString & _rPropertyName ) throw ( UnknownPropertyException , RuntimeException )
{
2007-07-06 07:48:27 +00:00
if ( _rPropertyName = = PROPERTY_ROWSET )
2008-12-01 12:31:27 +00:00
return : : comphelper : : OPropertyContainer : : getPropertyValue ( _rPropertyName ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
: : osl : : MutexGuard aGuard ( m_aMutex ) ;
return impl_getPropertyValue_throw ( _rPropertyName ) ;
}
//--------------------------------------------------------------------
void SAL_CALL FormComponentPropertyHandler : : setPropertyValue ( const : : rtl : : OUString & _rPropertyName , const Any & _rValue ) throw ( UnknownPropertyException , RuntimeException )
{
2007-07-06 07:48:27 +00:00
if ( _rPropertyName = = PROPERTY_ROWSET )
{
: : comphelper : : OPropertyContainer : : setPropertyValue ( _rPropertyName , _rValue ) ;
return ;
}
2008-12-01 12:31:27 +00:00
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
: : osl : : MutexGuard aGuard ( m_aMutex ) ;
2007-07-06 07:48:27 +00:00
PropertyId nPropId ( impl_getPropertyId_throw ( _rPropertyName ) ) ; // check if property is known by the handler
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
2008-12-01 12:31:27 +00:00
Reference < graphic : : XGraphicObject > xGrfObj ;
if ( PROPERTY_ID_IMAGE_URL = = nPropId & & ( _rValue > > = xGrfObj ) )
{
DBG_ASSERT ( xGrfObj . is ( ) , " FormComponentPropertyHandler::setPropertyValue() xGrfObj is invalid " ) ;
rtl : : OUString sObjectID ( RTL_CONSTASCII_USTRINGPARAM ( GRAPHOBJ_URLPREFIX ) ) ;
sObjectID = sObjectID + xGrfObj - > getUniqueID ( ) ;
m_xComponent - > setPropertyValue ( _rPropertyName , uno : : makeAny ( sObjectID ) ) ;
}
CWS-TOOLING: integrate CWS dba32b
2009-06-03 14:58:08 +0200 fs r272581 : #i102439#
2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls
2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font
2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary
2009-05-27 15:30:22 +0200 msc r272353 : #102303#
2009-05-26 13:03:06 +0200 fs r272295 : spelling
2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes
2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only
2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them
2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2
2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett
2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member
2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model
2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate
2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate
2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name
2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets
2009-05-20 11:29:55 +0200 msc r272111 : #i100000#
2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a
2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work
2009-05-20 09:43:36 +0200 oj r272106 : clean up includes
2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt
2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010#
2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey
2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset
2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column
2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names
2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date
2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date
2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019#
2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019#
2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010#
2009-05-15 10:21:24 +0200 msc r271929 : #101944#
2009-05-11 21:18:30 +0200 fs r271792 : #i99914#
2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span
2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode
2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue)
2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx
2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet
2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape
2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler
2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting
2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name
2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type
2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar
2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table
2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well
2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text
2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary
2009-05-07 11:47:18 +0200 fs r271647 : #i10000#
2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI
2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw
2009-05-07 10:09:55 +0200 fs r271634 : #i101623#
2009-05-07 09:53:44 +0200 fs r271631 : #i101622#
2009-05-06 21:55:53 +0200 fs r271615 : #i10000#
2009-05-06 21:10:42 +0200 fs r271611 : #i10000#
2009-05-06 13:11:48 +0200 fs r271583 : #i10000#
2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message
2009-05-05 22:29:03 +0200 fs r271558 : diagnostics
2009-05-05 22:16:16 +0200 fs r271557 : #i10000#
2009-05-05 13:50:32 +0200 fs r271513 : #i10000#
2009-05-05 10:21:50 +0200 fs r271503 : #i10000#
2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step?
2009-05-05 09:18:12 +0200 fs r271500 : #i10000#
2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47)
2009-05-04 14:51:26 +0200 fs r271456 : line ends
2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL
2009-04-22 21:18:34 +0200 fs r271141 : #i100944#
2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change
2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes
2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes
2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes
2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before
2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed
2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows
2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart
2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter
2009-04-17 21:00:23 +0200 fs r270954 : #i98350#
2009-04-17 13:54:19 +0200 fs r270942 : #i99565#
2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model
2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include
2009-04-17 10:10:15 +0200 fs r270926 : #i10000#
2009-04-17 10:02:36 +0200 fs r270925 : #i10000#
2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx
2009-04-16 21:05:25 +0200 fs r270903 : #i10000#
2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual
2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property
2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too
2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-15 14:53:13 +0200 fs r270844 : #i10000#
2009-04-15 13:08:29 +0200 fs r270836 : #i10000#
2009-04-15 12:28:14 +0200 fs r270832 : #i10000#
2009-04-15 10:59:14 +0200 fs r270827 : #i10000#
2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd
2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified
2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj
2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType
2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property
2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx
2009-04-14 15:46:54 +0200 fs r270784 : diagnostics
2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context
2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const
2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces
2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2
2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest
2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height
2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well
2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns
2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report
2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report
2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report
2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report
2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends
2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report
2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report
2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report
2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report
2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report
2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report
2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein
2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary
2009-04-03 14:35:49 +0200 fs r270487 : #i10000#
2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too
2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties
2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it
2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position
2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name
2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein
2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics
2009-04-02 16:35:19 +0200 fs r270421 : diagnostics
2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead
2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters
2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein
2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein
2009-04-02 14:10:35 +0200 fs r270405 : #i10000#
2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein
2009-04-02 14:03:03 +0200 fs r270401 : #i10000#
2009-04-02 13:58:13 +0200 fs r270400 : #i10000#
2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein
2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes
2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein
2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein
2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header
2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein
2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein
2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein
2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types
2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein
2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein
2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein
2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/>
2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used
2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode
2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein
2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge
2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein
2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein
2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table
2009-03-30 09:36:24 +0200 fs r270195 : assertion text
2009-03-28 20:21:58 +0100 fs r270187 : #ii10000#
2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids
2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids
2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset
2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45)
2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes
2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring
2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths
2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values
2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN
2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN
2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter
2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys
2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox
2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition
2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button
2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition
2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition
2009-03-25 10:29:07 +0100 fs r270003 : add missing localization
2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed
2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb
2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation
2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb
2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control
2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK
2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style
2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust
2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type
2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb
2009-03-20 08:52:47 +0100 fs r269780 : doc
2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different
2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider
2009-03-19 22:52:52 +0100 fs r269771 : added comment
2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration
2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now.
2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object
2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups
2009-03-19 09:25:27 +0100 fs r269727 : #i10000#
2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance
2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks
2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation
2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency
2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports
2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet)
2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work
2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation
2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext
2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long
2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null
2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params
2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment
2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed
2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment
2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle
2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups
2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList
2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface
2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList
2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups
2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups
2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion
2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode
2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode
2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes
2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long
2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents
2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive
2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header
2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type
2009-03-16 14:14:16 +0100 fs r269537 : line ends
2009-03-16 14:11:06 +0100 fs r269535 : line ends
2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter
2009-03-16 12:30:31 +0100 oj r269521 : compile error
2009-03-16 12:19:12 +0100 oj r269519 : compile error
2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap
2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43)
2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :)
2009-03-12 14:35:07 +0100 fs r269414 : not needed
2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module
2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib
2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure)
2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move
2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk
2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore
2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:45:07 +0100 fs r269401 : moved from ../
2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider
2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error
2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests
2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat
2009-03-12 12:34:53 +0100 fs r269388 : new API tests
2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed
2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring
2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop
2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider
2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop
2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications
2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications
2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications
2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components
2009-03-12 10:30:37 +0100 fs r269367 : module-local includes
2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata
2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name
2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty
2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language
2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer
2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map
2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer
2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied
2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed
2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults
2009-03-06 17:20:30 +0100 fs r269029 : #i98600#
2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ...
2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed
2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option
2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now
2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms
2009-03-06 09:53:41 +0100 fs r268977 : #i10000#
2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems
2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted)
2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20
2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages
2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42
2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings
2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups
2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b
2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b
2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData
2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations
2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL
2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types
2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator !=
2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size
2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now
2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric
2009-02-19 15:43:12 +0100 fs r268291 : #i99415#
2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account
2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title
2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
else if ( PROPERTY_ID_FONT = = nPropId )
2006-03-31 11:19:30 +00:00
{
// special handling, the value is a faked value we generated ourself in impl_executeFontDialog_nothrow
Sequence < NamedValue > aFontPropertyValues ;
OSL_VERIFY ( _rValue > > = aFontPropertyValues ) ;
const NamedValue * fontPropertyValue = aFontPropertyValues . getConstArray ( ) ;
const NamedValue * fontPropertyValueEnd = fontPropertyValue + aFontPropertyValues . getLength ( ) ;
for ( ; fontPropertyValue ! = fontPropertyValueEnd ; + + fontPropertyValue )
m_xComponent - > setPropertyValue ( fontPropertyValue - > Name , fontPropertyValue - > Value ) ;
}
else
2007-01-02 14:53:53 +00:00
{
Any aValue = _rValue ;
Reference < resource : : XStringResourceResolver > xStringResourceResolver
= lcl_getStringResourceResolverForProperty ( m_xComponent , _rPropertyName , _rValue ) ;
if ( xStringResourceResolver . is ( ) )
{
Reference < resource : : XStringResourceManager >
xStringResourceManager ( xStringResourceResolver , UNO_QUERY ) ;
if ( xStringResourceManager . is ( ) )
{
Any aPropertyValue ( m_xComponent - > getPropertyValue ( _rPropertyName ) ) ;
2007-01-29 15:57:30 +00:00
TypeClass eType = aPropertyValue . getValueType ( ) . getTypeClass ( ) ;
if ( eType = = TypeClass_STRING )
2007-01-02 14:53:53 +00:00
{
2007-01-29 15:57:30 +00:00
: : rtl : : OUString aPropStr ;
aPropertyValue > > = aPropStr ;
if ( aPropStr . getLength ( ) > 1 )
{
: : rtl : : OUString aPureIdStr = aPropStr . copy ( 1 ) ;
: : rtl : : OUString aValueStr ;
_rValue > > = aValueStr ;
xStringResourceManager - > setString ( aPureIdStr , aValueStr ) ;
aValue = aPropertyValue ; // set value to force modified
}
}
// StringItemList?
else if ( eType = = TypeClass_SEQUENCE )
{
static : : rtl : : OUString aDot = : : rtl : : OUString : : createFromAscii ( " . " ) ;
static : : rtl : : OUString aEsc = : : rtl : : OUString : : createFromAscii ( " & " ) ;
// Put strings into resource using new ids
Sequence < : : rtl : : OUString > aNewStrings ;
_rValue > > = aNewStrings ;
const : : rtl : : OUString * pNewStrings = aNewStrings . getConstArray ( ) ;
sal_Int32 nNewCount = aNewStrings . getLength ( ) ;
// Create new Ids
: : rtl : : OUString * pNewPureIds = new : : rtl : : OUString [ nNewCount ] ;
: : rtl : : OUString aIdStrBase = aDot ;
Any aNameAny = m_xComponent - > getPropertyValue ( PROPERTY_NAME ) ;
: : rtl : : OUString sControlName ;
aNameAny > > = sControlName ;
aIdStrBase + = sControlName ;
aIdStrBase + = aDot ;
aIdStrBase + = _rPropertyName ;
sal_Int32 i ;
: : rtl : : OUString aDummyStr ;
for ( i = 0 ; i < nNewCount ; + + i )
{
sal_Int32 nUniqueId = xStringResourceManager - > getUniqueNumericId ( ) ;
: : rtl : : OUString aPureIdStr = : : rtl : : OUString : : valueOf ( nUniqueId ) ;
aPureIdStr + = aIdStrBase ;
pNewPureIds [ i ] = aPureIdStr ;
// Force usage of next Unique Id
xStringResourceManager - > setString ( aPureIdStr , aDummyStr ) ;
}
// Move strings to new Ids for all locales
Sequence < Locale > aLocaleSeq = xStringResourceManager - > getLocales ( ) ;
const Locale * pLocale = aLocaleSeq . getConstArray ( ) ;
sal_Int32 nLocaleCount = aLocaleSeq . getLength ( ) ;
Sequence < : : rtl : : OUString > aOldIdStrings ;
aPropertyValue > > = aOldIdStrings ;
try
{
const : : rtl : : OUString * pOldIdStrings = aOldIdStrings . getConstArray ( ) ;
sal_Int32 nOldIdCount = aOldIdStrings . getLength ( ) ;
for ( i = 0 ; i < nNewCount ; + + i )
{
: : rtl : : OUString aOldIdStr ;
: : rtl : : OUString aOldPureIdStr ;
if ( i < nOldIdCount )
{
aOldIdStr = pOldIdStrings [ i ] ;
aOldPureIdStr = aOldIdStr . copy ( 1 ) ;
}
: : rtl : : OUString aNewPureIdStr = pNewPureIds [ i ] ;
for ( sal_Int32 iLocale = 0 ; iLocale < nLocaleCount ; + + iLocale )
{
Locale aLocale = pLocale [ iLocale ] ;
: : rtl : : OUString aResourceStr ;
if ( aOldPureIdStr . getLength ( ) ! = 0 )
{
if ( xStringResourceManager - > hasEntryForIdAndLocale ( aOldPureIdStr , aLocale ) )
{
aResourceStr = xStringResourceManager - >
resolveStringForLocale ( aOldPureIdStr , aLocale ) ;
}
}
xStringResourceManager - > setStringForLocale ( aNewPureIdStr , aResourceStr , aLocale ) ;
}
}
}
catch ( resource : : MissingResourceException & )
{ }
// Set new strings for current locale and create
// new Id sequence as new property value
Sequence < : : rtl : : OUString > aNewIdStrings ;
aNewIdStrings . realloc ( nNewCount ) ;
: : rtl : : OUString * pNewIdStrings = aNewIdStrings . getArray ( ) ;
for ( i = 0 ; i < nNewCount ; + + i )
{
: : rtl : : OUString aPureIdStr = pNewPureIds [ i ] ;
: : rtl : : OUString aStr = pNewStrings [ i ] ;
xStringResourceManager - > setString ( aPureIdStr , aStr ) ;
: : rtl : : OUString aIdStr = aEsc ;
aIdStr + = aPureIdStr ;
pNewIdStrings [ i ] = aIdStr ;
}
aValue < < = aNewIdStrings ;
// Remove old ids from resource for all locales
const : : rtl : : OUString * pOldIdStrings = aOldIdStrings . getConstArray ( ) ;
sal_Int32 nOldIdCount = aOldIdStrings . getLength ( ) ;
for ( i = 0 ; i < nOldIdCount ; + + i )
{
: : rtl : : OUString aIdStr = pOldIdStrings [ i ] ;
: : rtl : : OUString aPureIdStr = aIdStr . copy ( 1 ) ;
for ( sal_Int32 iLocale = 0 ; iLocale < nLocaleCount ; + + iLocale )
{
Locale aLocale = pLocale [ iLocale ] ;
try
{
xStringResourceManager - > removeIdForLocale ( aPureIdStr , aLocale ) ;
}
catch ( resource : : MissingResourceException & )
{ }
}
}
delete [ ] pNewPureIds ;
2007-01-02 14:53:53 +00:00
}
}
}
m_xComponent - > setPropertyValue ( _rPropertyName , aValue ) ;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
//--------------------------------------------------------------------
Any SAL_CALL FormComponentPropertyHandler : : convertToPropertyValue ( const : : rtl : : OUString & _rPropertyName , const Any & _rControlValue ) throw ( UnknownPropertyException , RuntimeException )
{
: : osl : : MutexGuard aGuard ( m_aMutex ) ;
PropertyId nPropId ( impl_getPropertyId_throw ( _rPropertyName ) ) ;
Property aProperty ( impl_getPropertyFromId_throw ( nPropId ) ) ;
Any aPropertyValue ( _rControlValue ) ;
if ( ! aPropertyValue . hasValue ( ) )
{
if ( ( aProperty . Attributes & PropertyAttribute : : MAYBEVOID ) = = 0 )
// default construct an instance of the proper type
aPropertyValue = Any ( NULL , aProperty . Type ) ;
// nothing to do
return aPropertyValue ;
}
/// care for the special "default" string, translate it to VOID
if ( m_aPropertiesWithDefListEntry . find ( _rPropertyName ) ! = m_aPropertiesWithDefListEntry . end ( ) )
{
// it's a control with a string list
: : rtl : : OUString sStringValue ;
if ( _rControlValue > > = sStringValue )
{ // note that ColorListBoxes might transfer values either as string or as css.util.Color,
// so this check here is important
if ( sStringValue = = m_sDefaultValueString )
return Any ( ) ;
}
}
switch ( nPropId )
{
case PROPERTY_ID_DATASOURCE :
{
: : rtl : : OUString sControlValue ;
OSL_VERIFY ( _rControlValue > > = sControlValue ) ;
if ( sControlValue . getLength ( ) )
{
Reference < XNameAccess > xDatabaseContext ;
m_aContext . createComponent ( ( : : rtl : : OUString ) SERVICE_DATABASE_CONTEXT , xDatabaseContext ) ;
if ( ! xDatabaseContext . is ( ) | | ! xDatabaseContext - > hasByName ( sControlValue ) )
{
: : svt : : OFileNotation aTransformer ( sControlValue ) ;
aPropertyValue < < = : : rtl : : OUString ( aTransformer . get ( : : svt : : OFileNotation : : N_URL ) ) ;
}
}
}
break ; // case PROPERTY_ID_DATASOURCE
case PROPERTY_ID_SHOW_POSITION :
case PROPERTY_ID_SHOW_NAVIGATION :
case PROPERTY_ID_SHOW_RECORDACTIONS :
case PROPERTY_ID_SHOW_FILTERSORT :
{
: : rtl : : OUString sControlValue ;
OSL_VERIFY ( _rControlValue > > = sControlValue ) ;
2009-04-24 18:34:24 +00:00
: : std : : vector < : : rtl : : OUString > aListEntries ;
tools : : StringListResource aRes ( PcrRes ( RID_RSC_ENUM_SHOWHIDE ) , aListEntries ) ;
OSL_ENSURE ( aListEntries . size ( ) = = 2 , " FormComponentPropertyHandler::convertToPropertyValue: broken resource for Show/Hide! " ) ;
sal_Bool bShow = ( aListEntries . size ( ) < 2 ) | | ( sControlValue = = aListEntries [ 1 ] ) ;
aPropertyValue < < = bShow ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
break ;
case PROPERTY_ID_TARGET_URL :
case PROPERTY_ID_IMAGE_URL :
{
: : rtl : : OUString sControlValue ;
OSL_VERIFY ( _rControlValue > > = sControlValue ) ;
2008-12-01 12:31:27 +00:00
// Don't convert a placeholder
if ( nPropId = = PROPERTY_ID_IMAGE_URL & & sControlValue . equals ( String ( PcrRes ( RID_EMBED_IMAGE_PLACEHOLDER ) ) ) )
aPropertyValue < < = sControlValue ;
else
{
INetURLObject aDocURL ( impl_getDocumentURL_nothrow ( ) ) ;
aPropertyValue < < = ( : : rtl : : OUString ) URIHelper : : SmartRel2Abs ( aDocURL , sControlValue , Link ( ) , false , true , INetURLObject : : WAS_ENCODED , INetURLObject : : DECODE_TO_IURI ) ;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
break ;
case PROPERTY_ID_DATEMIN :
case PROPERTY_ID_DATEMAX :
case PROPERTY_ID_DEFAULT_DATE :
case PROPERTY_ID_DATE :
{
util : : Date aDate ;
OSL_VERIFY ( _rControlValue > > = aDate ) ;
aPropertyValue < < = ( sal_Int32 ) DBTypeConversion : : toINT32 ( aDate ) ;
}
break ;
case PROPERTY_ID_TIMEMIN :
case PROPERTY_ID_TIMEMAX :
case PROPERTY_ID_DEFAULT_TIME :
case PROPERTY_ID_TIME :
{
util : : Time aTime ;
OSL_VERIFY ( _rControlValue > > = aTime ) ;
aPropertyValue < < = ( sal_Int32 ) DBTypeConversion : : toINT32 ( aTime ) ;
}
break ;
2008-12-16 13:30:53 +00:00
case PROPERTY_ID_WRITING_MODE :
{
aPropertyValue = FormComponentPropertyHandler_Base : : convertToPropertyValue ( _rPropertyName , _rControlValue ) ;
sal_Int16 nNormalizedValue ( 2 ) ;
OSL_VERIFY ( aPropertyValue > > = nNormalizedValue ) ;
sal_Int16 nWritingMode = WritingMode2 : : CONTEXT ;
switch ( nNormalizedValue )
{
case 0 : nWritingMode = WritingMode2 : : LR_TB ; break ;
case 1 : nWritingMode = WritingMode2 : : RL_TB ; break ;
case 2 : nWritingMode = WritingMode2 : : CONTEXT ; break ;
default :
CWS-TOOLING: integrate CWS dba32b
2009-06-03 14:58:08 +0200 fs r272581 : #i102439#
2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls
2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font
2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary
2009-05-27 15:30:22 +0200 msc r272353 : #102303#
2009-05-26 13:03:06 +0200 fs r272295 : spelling
2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes
2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only
2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them
2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2
2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett
2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member
2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model
2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate
2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate
2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name
2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets
2009-05-20 11:29:55 +0200 msc r272111 : #i100000#
2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a
2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work
2009-05-20 09:43:36 +0200 oj r272106 : clean up includes
2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt
2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010#
2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey
2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset
2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column
2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names
2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date
2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date
2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019#
2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019#
2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010#
2009-05-15 10:21:24 +0200 msc r271929 : #101944#
2009-05-11 21:18:30 +0200 fs r271792 : #i99914#
2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span
2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode
2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue)
2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx
2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet
2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape
2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler
2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting
2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name
2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type
2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar
2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table
2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well
2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text
2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary
2009-05-07 11:47:18 +0200 fs r271647 : #i10000#
2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI
2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw
2009-05-07 10:09:55 +0200 fs r271634 : #i101623#
2009-05-07 09:53:44 +0200 fs r271631 : #i101622#
2009-05-06 21:55:53 +0200 fs r271615 : #i10000#
2009-05-06 21:10:42 +0200 fs r271611 : #i10000#
2009-05-06 13:11:48 +0200 fs r271583 : #i10000#
2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message
2009-05-05 22:29:03 +0200 fs r271558 : diagnostics
2009-05-05 22:16:16 +0200 fs r271557 : #i10000#
2009-05-05 13:50:32 +0200 fs r271513 : #i10000#
2009-05-05 10:21:50 +0200 fs r271503 : #i10000#
2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step?
2009-05-05 09:18:12 +0200 fs r271500 : #i10000#
2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47)
2009-05-04 14:51:26 +0200 fs r271456 : line ends
2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL
2009-04-22 21:18:34 +0200 fs r271141 : #i100944#
2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change
2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes
2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes
2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes
2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before
2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed
2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows
2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart
2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter
2009-04-17 21:00:23 +0200 fs r270954 : #i98350#
2009-04-17 13:54:19 +0200 fs r270942 : #i99565#
2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model
2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include
2009-04-17 10:10:15 +0200 fs r270926 : #i10000#
2009-04-17 10:02:36 +0200 fs r270925 : #i10000#
2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx
2009-04-16 21:05:25 +0200 fs r270903 : #i10000#
2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual
2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property
2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too
2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-15 14:53:13 +0200 fs r270844 : #i10000#
2009-04-15 13:08:29 +0200 fs r270836 : #i10000#
2009-04-15 12:28:14 +0200 fs r270832 : #i10000#
2009-04-15 10:59:14 +0200 fs r270827 : #i10000#
2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd
2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified
2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj
2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType
2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property
2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx
2009-04-14 15:46:54 +0200 fs r270784 : diagnostics
2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context
2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const
2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces
2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2
2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest
2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height
2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well
2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns
2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report
2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report
2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report
2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report
2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends
2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report
2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report
2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report
2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report
2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report
2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report
2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein
2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary
2009-04-03 14:35:49 +0200 fs r270487 : #i10000#
2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too
2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties
2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it
2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position
2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name
2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein
2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics
2009-04-02 16:35:19 +0200 fs r270421 : diagnostics
2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead
2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters
2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein
2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein
2009-04-02 14:10:35 +0200 fs r270405 : #i10000#
2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein
2009-04-02 14:03:03 +0200 fs r270401 : #i10000#
2009-04-02 13:58:13 +0200 fs r270400 : #i10000#
2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein
2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes
2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein
2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein
2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header
2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein
2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein
2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein
2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types
2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein
2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein
2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein
2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/>
2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used
2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode
2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein
2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge
2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein
2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein
2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table
2009-03-30 09:36:24 +0200 fs r270195 : assertion text
2009-03-28 20:21:58 +0100 fs r270187 : #ii10000#
2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids
2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids
2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset
2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45)
2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes
2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring
2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths
2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values
2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN
2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN
2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter
2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys
2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox
2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition
2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button
2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition
2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition
2009-03-25 10:29:07 +0100 fs r270003 : add missing localization
2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed
2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb
2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation
2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb
2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control
2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK
2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style
2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust
2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type
2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb
2009-03-20 08:52:47 +0100 fs r269780 : doc
2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different
2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider
2009-03-19 22:52:52 +0100 fs r269771 : added comment
2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration
2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now.
2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object
2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups
2009-03-19 09:25:27 +0100 fs r269727 : #i10000#
2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance
2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks
2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation
2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency
2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports
2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet)
2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work
2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation
2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext
2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long
2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null
2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params
2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment
2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed
2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment
2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle
2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups
2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList
2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface
2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList
2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups
2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups
2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion
2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode
2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode
2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes
2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long
2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents
2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive
2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header
2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type
2009-03-16 14:14:16 +0100 fs r269537 : line ends
2009-03-16 14:11:06 +0100 fs r269535 : line ends
2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter
2009-03-16 12:30:31 +0100 oj r269521 : compile error
2009-03-16 12:19:12 +0100 oj r269519 : compile error
2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap
2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43)
2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :)
2009-03-12 14:35:07 +0100 fs r269414 : not needed
2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module
2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib
2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure)
2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move
2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk
2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore
2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:45:07 +0100 fs r269401 : moved from ../
2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider
2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error
2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests
2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat
2009-03-12 12:34:53 +0100 fs r269388 : new API tests
2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed
2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring
2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop
2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider
2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop
2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications
2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications
2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications
2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components
2009-03-12 10:30:37 +0100 fs r269367 : module-local includes
2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata
2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name
2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty
2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language
2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer
2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map
2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer
2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied
2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed
2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults
2009-03-06 17:20:30 +0100 fs r269029 : #i98600#
2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ...
2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed
2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option
2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now
2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms
2009-03-06 09:53:41 +0100 fs r268977 : #i10000#
2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems
2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted)
2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20
2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages
2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42
2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings
2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups
2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b
2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b
2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData
2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations
2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL
2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types
2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator !=
2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size
2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now
2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric
2009-02-19 15:43:12 +0100 fs r268291 : #i99415#
2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account
2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title
2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
OSL_ENSURE ( false , " FormComponentPropertyHandler::convertToPropertyValue: unexpected 'normalized value' for WritingMode! " ) ;
2008-12-16 13:30:53 +00:00
nWritingMode = WritingMode2 : : CONTEXT ;
break ;
}
aPropertyValue < < = nWritingMode ;
}
break ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
default :
aPropertyValue = FormComponentPropertyHandler_Base : : convertToPropertyValue ( _rPropertyName , _rControlValue ) ;
break ; // default
} // switch ( nPropId )
return aPropertyValue ;
}
//--------------------------------------------------------------------
Any SAL_CALL FormComponentPropertyHandler : : convertToControlValue ( const : : rtl : : OUString & _rPropertyName , const Any & _rPropertyValue , const Type & _rControlValueType ) throw ( UnknownPropertyException , RuntimeException )
{
: : osl : : MutexGuard aGuard ( m_aMutex ) ;
sal_Int32 nPropId = m_pInfoService - > getPropertyId ( _rPropertyName ) ;
DBG_ASSERT ( nPropId ! = - 1 , " FormComponentPropertyHandler::convertToPropertyValue: not one of my properties!! " ) ;
Property aProperty ( impl_getPropertyFromId_throw ( nPropId ) ) ;
Any aControlValue ( _rPropertyValue ) ;
if ( ! aControlValue . hasValue ( ) )
{
// if the property is represented with a list box or color list box, we need to
// translate this into the string "Default"
if ( m_aPropertiesWithDefListEntry . find ( _rPropertyName ) ! = m_aPropertiesWithDefListEntry . end ( ) )
aControlValue < < = m_sDefaultValueString ;
return aControlValue ;
}
switch ( nPropId )
{
//////////////////////////////////////////////////////////////
case PROPERTY_ID_SHOW_POSITION :
case PROPERTY_ID_SHOW_NAVIGATION :
case PROPERTY_ID_SHOW_RECORDACTIONS :
case PROPERTY_ID_SHOW_FILTERSORT :
{
2009-04-24 18:34:24 +00:00
: : std : : vector < : : rtl : : OUString > aListEntries ;
tools : : StringListResource aRes ( PcrRes ( RID_RSC_ENUM_SHOWHIDE ) , aListEntries ) ;
OSL_ENSURE ( aListEntries . size ( ) = = 2 , " FormComponentPropertyHandler::convertToControlValue: broken resource for Show/Hide! " ) ;
if ( aListEntries . size ( ) = = 2 )
{
: : rtl : : OUString sControlValue = : : comphelper : : getBOOL ( _rPropertyValue )
? aListEntries [ 1 ]
: aListEntries [ 0 ] ;
aControlValue < < = sControlValue ;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
break ;
//////////////////////////////////////////////////////////////
case PROPERTY_ID_DATASOURCE :
{
OSL_ENSURE ( _rControlValueType . getTypeClass ( ) = = TypeClass_STRING ,
" FormComponentPropertyHandler::convertToControlValue: wrong ControlValueType! " ) ;
: : rtl : : OUString sDataSource ;
_rPropertyValue > > = sDataSource ;
if ( sDataSource . getLength ( ) )
{
: : svt : : OFileNotation aTransformer ( sDataSource ) ;
sDataSource = aTransformer . get ( : : svt : : OFileNotation : : N_SYSTEM ) ;
}
aControlValue < < = sDataSource ;
}
break ;
//////////////////////////////////////////////////////////////
case PROPERTY_ID_CONTROLLABEL :
{
: : rtl : : OUString sControlValue ;
Reference < XPropertySet > xSet ;
_rPropertyValue > > = xSet ;
Reference < XPropertySetInfo > xPSI ;
if ( xSet . is ( ) )
xPSI = xSet - > getPropertySetInfo ( ) ;
if ( xPSI . is ( ) & & xPSI - > hasPropertyByName ( PROPERTY_LABEL ) )
{
: : rtl : : OUStringBuffer aValue ;
aValue . append ( ( sal_Unicode ) ' < ' ) ;
: : rtl : : OUString sLabel ;
OSL_VERIFY ( xSet - > getPropertyValue ( PROPERTY_LABEL ) > > = sLabel ) ;
aValue . append ( sLabel ) ;
aValue . append ( ( sal_Unicode ) ' > ' ) ;
sControlValue = aValue . makeStringAndClear ( ) ;
}
aControlValue < < = sControlValue ;
}
break ;
//////////////////////////////////////////////////////////////
case PROPERTY_ID_DATEMIN :
case PROPERTY_ID_DATEMAX :
case PROPERTY_ID_DEFAULT_DATE :
case PROPERTY_ID_DATE :
{
sal_Int32 nDate = 0 ;
OSL_VERIFY ( _rPropertyValue > > = nDate ) ;
aControlValue < < = DBTypeConversion : : toDate ( nDate ) ;
}
break ;
case PROPERTY_ID_TIMEMIN :
case PROPERTY_ID_TIMEMAX :
case PROPERTY_ID_DEFAULT_TIME :
case PROPERTY_ID_TIME :
{
sal_Int32 nTime = 0 ;
OSL_VERIFY ( _rPropertyValue > > = nTime ) ;
aControlValue < < = DBTypeConversion : : toTime ( nTime ) ;
}
break ;
2008-12-16 13:30:53 +00:00
case PROPERTY_ID_WRITING_MODE :
{
sal_Int16 nWritingMode ( WritingMode2 : : CONTEXT ) ;
OSL_VERIFY ( _rPropertyValue > > = nWritingMode ) ;
sal_Int16 nNormalized = 2 ;
switch ( nWritingMode )
{
case WritingMode2 : : LR_TB : nNormalized = 0 ; break ;
case WritingMode2 : : RL_TB : nNormalized = 1 ; break ;
case WritingMode2 : : CONTEXT : nNormalized = 2 ; break ;
default :
OSL_ENSURE ( false , " FormComponentPropertyHandler::convertToControlValue: unsupported API value for WritingMode! " ) ;
nNormalized = 2 ;
break ;
}
aControlValue = FormComponentPropertyHandler_Base : : convertToControlValue ( _rPropertyName , makeAny ( nNormalized ) , _rControlValueType ) ;
}
break ;
CWS-TOOLING: integrate CWS dba32b
2009-06-03 14:58:08 +0200 fs r272581 : #i102439#
2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls
2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font
2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary
2009-05-27 15:30:22 +0200 msc r272353 : #102303#
2009-05-26 13:03:06 +0200 fs r272295 : spelling
2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes
2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only
2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them
2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2
2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett
2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member
2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model
2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate
2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate
2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name
2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets
2009-05-20 11:29:55 +0200 msc r272111 : #i100000#
2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a
2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work
2009-05-20 09:43:36 +0200 oj r272106 : clean up includes
2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt
2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010#
2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey
2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset
2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column
2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names
2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date
2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date
2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019#
2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019#
2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010#
2009-05-15 10:21:24 +0200 msc r271929 : #101944#
2009-05-11 21:18:30 +0200 fs r271792 : #i99914#
2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span
2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode
2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue)
2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx
2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet
2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape
2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler
2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting
2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name
2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type
2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar
2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table
2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well
2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text
2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary
2009-05-07 11:47:18 +0200 fs r271647 : #i10000#
2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI
2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw
2009-05-07 10:09:55 +0200 fs r271634 : #i101623#
2009-05-07 09:53:44 +0200 fs r271631 : #i101622#
2009-05-06 21:55:53 +0200 fs r271615 : #i10000#
2009-05-06 21:10:42 +0200 fs r271611 : #i10000#
2009-05-06 13:11:48 +0200 fs r271583 : #i10000#
2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message
2009-05-05 22:29:03 +0200 fs r271558 : diagnostics
2009-05-05 22:16:16 +0200 fs r271557 : #i10000#
2009-05-05 13:50:32 +0200 fs r271513 : #i10000#
2009-05-05 10:21:50 +0200 fs r271503 : #i10000#
2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step?
2009-05-05 09:18:12 +0200 fs r271500 : #i10000#
2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47)
2009-05-04 14:51:26 +0200 fs r271456 : line ends
2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL
2009-04-22 21:18:34 +0200 fs r271141 : #i100944#
2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change
2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes
2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes
2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes
2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before
2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed
2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows
2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart
2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter
2009-04-17 21:00:23 +0200 fs r270954 : #i98350#
2009-04-17 13:54:19 +0200 fs r270942 : #i99565#
2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model
2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include
2009-04-17 10:10:15 +0200 fs r270926 : #i10000#
2009-04-17 10:02:36 +0200 fs r270925 : #i10000#
2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx
2009-04-16 21:05:25 +0200 fs r270903 : #i10000#
2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual
2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property
2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too
2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-15 14:53:13 +0200 fs r270844 : #i10000#
2009-04-15 13:08:29 +0200 fs r270836 : #i10000#
2009-04-15 12:28:14 +0200 fs r270832 : #i10000#
2009-04-15 10:59:14 +0200 fs r270827 : #i10000#
2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd
2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified
2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj
2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType
2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property
2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx
2009-04-14 15:46:54 +0200 fs r270784 : diagnostics
2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context
2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const
2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces
2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2
2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest
2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height
2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well
2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns
2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report
2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report
2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report
2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report
2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends
2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report
2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report
2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report
2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report
2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report
2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report
2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein
2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary
2009-04-03 14:35:49 +0200 fs r270487 : #i10000#
2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too
2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties
2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it
2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position
2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name
2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein
2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics
2009-04-02 16:35:19 +0200 fs r270421 : diagnostics
2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead
2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters
2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein
2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein
2009-04-02 14:10:35 +0200 fs r270405 : #i10000#
2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein
2009-04-02 14:03:03 +0200 fs r270401 : #i10000#
2009-04-02 13:58:13 +0200 fs r270400 : #i10000#
2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein
2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes
2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein
2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein
2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header
2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein
2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein
2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein
2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types
2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein
2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein
2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein
2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/>
2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used
2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode
2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein
2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge
2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein
2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein
2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table
2009-03-30 09:36:24 +0200 fs r270195 : assertion text
2009-03-28 20:21:58 +0100 fs r270187 : #ii10000#
2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids
2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids
2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset
2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45)
2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes
2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring
2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths
2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values
2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN
2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN
2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter
2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys
2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox
2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition
2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button
2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition
2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition
2009-03-25 10:29:07 +0100 fs r270003 : add missing localization
2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed
2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb
2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation
2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb
2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control
2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK
2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style
2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust
2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type
2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb
2009-03-20 08:52:47 +0100 fs r269780 : doc
2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different
2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider
2009-03-19 22:52:52 +0100 fs r269771 : added comment
2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration
2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now.
2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object
2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups
2009-03-19 09:25:27 +0100 fs r269727 : #i10000#
2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance
2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks
2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation
2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency
2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports
2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet)
2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work
2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation
2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext
2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long
2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null
2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params
2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment
2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed
2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment
2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle
2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups
2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList
2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface
2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList
2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups
2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups
2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion
2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode
2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode
2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes
2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long
2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents
2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive
2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header
2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type
2009-03-16 14:14:16 +0100 fs r269537 : line ends
2009-03-16 14:11:06 +0100 fs r269535 : line ends
2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter
2009-03-16 12:30:31 +0100 oj r269521 : compile error
2009-03-16 12:19:12 +0100 oj r269519 : compile error
2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap
2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43)
2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :)
2009-03-12 14:35:07 +0100 fs r269414 : not needed
2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module
2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib
2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure)
2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move
2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk
2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore
2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:45:07 +0100 fs r269401 : moved from ../
2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider
2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error
2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests
2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat
2009-03-12 12:34:53 +0100 fs r269388 : new API tests
2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed
2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring
2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop
2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider
2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop
2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications
2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications
2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications
2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components
2009-03-12 10:30:37 +0100 fs r269367 : module-local includes
2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata
2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name
2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty
2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language
2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer
2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map
2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer
2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied
2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed
2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults
2009-03-06 17:20:30 +0100 fs r269029 : #i98600#
2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ...
2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed
2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option
2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now
2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms
2009-03-06 09:53:41 +0100 fs r268977 : #i10000#
2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems
2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted)
2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20
2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages
2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42
2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings
2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups
2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b
2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b
2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData
2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations
2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL
2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types
2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator !=
2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size
2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now
2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric
2009-02-19 15:43:12 +0100 fs r268291 : #i99415#
2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account
2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title
2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
case PROPERTY_ID_FONT :
{
FontDescriptor aFont ;
OSL_VERIFY ( _rPropertyValue > > = aFont ) ;
: : rtl : : OUStringBuffer displayName ;
if ( ! aFont . Name . getLength ( ) )
{
displayName . append ( String ( PcrRes ( RID_STR_FONT_DEFAULT ) ) ) ;
}
else
{
// font name
displayName . append ( aFont . Name ) ;
displayName . appendAscii ( " , " ) ;
// font style
: : FontWeight eWeight = VCLUnoHelper : : ConvertFontWeight ( aFont . Weight ) ;
USHORT nStyleResID = RID_STR_FONTSTYLE_REGULAR ;
if ( aFont . Slant = = FontSlant_ITALIC )
{
if ( eWeight > WEIGHT_NORMAL )
nStyleResID = RID_STR_FONTSTYLE_BOLD_ITALIC ;
else
nStyleResID = RID_STR_FONTSTYLE_ITALIC ;
}
else
{
if ( eWeight > WEIGHT_NORMAL )
nStyleResID = RID_STR_FONTSTYLE_BOLD ;
}
displayName . append ( String ( PcrRes ( nStyleResID ) ) ) ;
// font size
if ( aFont . Height )
{
displayName . appendAscii ( " , " ) ;
displayName . append ( sal_Int32 ( aFont . Height ) ) ;
}
}
aControlValue < < = displayName . makeStringAndClear ( ) ;
}
break ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
default :
aControlValue = FormComponentPropertyHandler_Base : : convertToControlValue ( _rPropertyName , _rPropertyValue , _rControlValueType ) ;
break ;
} // switch ( nPropId )
return aControlValue ;
}
//--------------------------------------------------------------------
PropertyState SAL_CALL FormComponentPropertyHandler : : getPropertyState ( const : : rtl : : OUString & _rPropertyName ) throw ( UnknownPropertyException , RuntimeException )
{
: : osl : : MutexGuard aGuard ( m_aMutex ) ;
if ( m_xPropertyState . is ( ) )
return m_xPropertyState - > getPropertyState ( _rPropertyName ) ;
return PropertyState_DIRECT_VALUE ;
}
//--------------------------------------------------------------------
void SAL_CALL FormComponentPropertyHandler : : addPropertyChangeListener ( const Reference < XPropertyChangeListener > & _rxListener ) throw ( RuntimeException )
{
: : osl : : MutexGuard aGuard ( m_aMutex ) ;
FormComponentPropertyHandler_Base : : addPropertyChangeListener ( _rxListener ) ;
if ( m_xComponent . is ( ) )
m_xComponent - > addPropertyChangeListener ( : : rtl : : OUString ( ) , _rxListener ) ;
}
//--------------------------------------------------------------------
void SAL_CALL FormComponentPropertyHandler : : removePropertyChangeListener ( const Reference < XPropertyChangeListener > & _rxListener ) throw ( RuntimeException )
{
: : osl : : MutexGuard aGuard ( m_aMutex ) ;
if ( m_xComponent . is ( ) )
m_xComponent - > removePropertyChangeListener ( : : rtl : : OUString ( ) , _rxListener ) ;
FormComponentPropertyHandler_Base : : removePropertyChangeListener ( _rxListener ) ;
}
//--------------------------------------------------------------------
void FormComponentPropertyHandler : : onNewComponent ( )
{
FormComponentPropertyHandler_Base : : onNewComponent ( ) ;
if ( ! m_xComponentPropertyInfo . is ( ) & & m_xComponent . is ( ) )
throw NullPointerException ( ) ;
2007-07-06 07:48:27 +00:00
m_xPropertyState . set ( m_xComponent , UNO_QUERY ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
m_eComponentClass = eUnknown ;
m_bComponentIsSubForm = m_bHaveListSource = m_bHaveCommand = false ;
m_nClassId = 0 ;
impl_initComponentMetaData_throw ( ) ;
}
//--------------------------------------------------------------------
Sequence < Property > SAL_CALL FormComponentPropertyHandler : : doDescribeSupportedProperties ( ) const
{
if ( ! m_xComponentPropertyInfo . is ( ) )
return Sequence < Property > ( ) ;
: : std : : vector < Property > aProperties ;
Sequence < Property > aAllProperties ( m_xComponentPropertyInfo - > getProperties ( ) ) ;
aProperties . reserve ( aAllProperties . getLength ( ) ) ;
// filter the properties
PropertyId nPropId ( 0 ) ;
: : rtl : : OUString sDisplayName ;
Property * pProperty = aAllProperties . getArray ( ) ;
Property * pPropertiesEnd = pProperty + aAllProperties . getLength ( ) ;
for ( ; pProperty ! = pPropertiesEnd ; + + pProperty )
{
nPropId = m_pInfoService - > getPropertyId ( pProperty - > Name ) ;
if ( nPropId = = - 1 )
continue ;
pProperty - > Handle = nPropId ;
sDisplayName = m_pInfoService - > getPropertyTranslation ( nPropId ) ;
if ( ! sDisplayName . getLength ( ) )
continue ;
sal_uInt32 nPropertyUIFlags = m_pInfoService - > getPropertyUIFlags ( nPropId ) ;
bool bIsVisibleForForms = ( nPropertyUIFlags & PROP_FLAG_FORM_VISIBLE ) ! = 0 ;
bool bIsVisibleForDialogs = ( nPropertyUIFlags & PROP_FLAG_DIALOG_VISIBLE ) ! = 0 ;
// depending on whether we're working for a form or a UNO dialog, some
// properties are not displayed
if ( ( m_eComponentClass = = eFormControl & & ! bIsVisibleForForms )
| | ( m_eComponentClass = = eDialogControl & & ! bIsVisibleForDialogs )
)
continue ;
// some generic sanity checks
if ( impl_shouldExcludeProperty_nothrow ( * pProperty ) )
continue ;
switch ( nPropId )
{
case PROPERTY_ID_BORDER :
case PROPERTY_ID_TABSTOP :
// BORDER and TABSTOP are normalized (see impl_normalizePropertyValue_nothrow)
// to not allow VOID values
pProperty - > Attributes & = ~ ( PropertyAttribute : : MAYBEVOID ) ;
break ;
case PROPERTY_ID_LISTSOURCE :
// no cursor source if no Base is installed. #124939#
// This fix is not intendend to appear on the main trunk. If you find it there,
// please tell me! frank.schoenheit@sun.com
if ( SvtModuleOptions ( ) . IsModuleInstalled ( SvtModuleOptions : : E_SDATABASE ) )
const_cast < FormComponentPropertyHandler * > ( this ) - > m_bHaveListSource = true ;
break ;
case PROPERTY_ID_COMMAND :
// no cursor source if no Base is installed. #124939#
// This fix is not intendend to appear on the main trunk. If you find it there,
// please tell me! frank.schoenheit@sun.com
if ( SvtModuleOptions ( ) . IsModuleInstalled ( SvtModuleOptions : : E_SDATABASE ) )
const_cast < FormComponentPropertyHandler * > ( this ) - > m_bHaveCommand = true ;
break ;
} // switch ( nPropId )
aProperties . push_back ( * pProperty ) ;
}
if ( aProperties . empty ( ) )
return Sequence < Property > ( ) ;
return Sequence < Property > ( & ( * aProperties . begin ( ) ) , aProperties . size ( ) ) ;
}
//--------------------------------------------------------------------
Sequence < : : rtl : : OUString > SAL_CALL FormComponentPropertyHandler : : getSupersededProperties ( ) throw ( RuntimeException )
{
return Sequence < : : rtl : : OUString > ( ) ;
}
//--------------------------------------------------------------------
Sequence < : : rtl : : OUString > SAL_CALL FormComponentPropertyHandler : : getActuatingProperties ( ) throw ( RuntimeException )
{
: : osl : : MutexGuard aGuard ( m_aMutex ) ;
: : std : : vector < : : rtl : : OUString > aInterestingProperties ;
aInterestingProperties . push_back ( PROPERTY_DATASOURCE ) ;
aInterestingProperties . push_back ( PROPERTY_COMMAND ) ;
aInterestingProperties . push_back ( PROPERTY_COMMANDTYPE ) ;
aInterestingProperties . push_back ( PROPERTY_LISTSOURCE ) ;
aInterestingProperties . push_back ( PROPERTY_LISTSOURCETYPE ) ;
aInterestingProperties . push_back ( PROPERTY_SUBMIT_ENCODING ) ;
aInterestingProperties . push_back ( PROPERTY_REPEAT ) ;
aInterestingProperties . push_back ( PROPERTY_TABSTOP ) ;
aInterestingProperties . push_back ( PROPERTY_BORDER ) ;
aInterestingProperties . push_back ( PROPERTY_CONTROLSOURCE ) ;
aInterestingProperties . push_back ( PROPERTY_DROPDOWN ) ;
aInterestingProperties . push_back ( PROPERTY_IMAGE_URL ) ;
aInterestingProperties . push_back ( PROPERTY_TARGET_URL ) ;
aInterestingProperties . push_back ( PROPERTY_STRINGITEMLIST ) ;
aInterestingProperties . push_back ( PROPERTY_BUTTONTYPE ) ;
aInterestingProperties . push_back ( PROPERTY_ESCAPE_PROCESSING ) ;
aInterestingProperties . push_back ( PROPERTY_TRISTATE ) ;
aInterestingProperties . push_back ( PROPERTY_DECIMAL_ACCURACY ) ;
aInterestingProperties . push_back ( PROPERTY_SHOWTHOUSANDSEP ) ;
aInterestingProperties . push_back ( PROPERTY_FORMATKEY ) ;
2008-12-01 12:31:27 +00:00
aInterestingProperties . push_back ( PROPERTY_EMPTY_IS_NULL ) ;
CWS-TOOLING: integrate CWS dba32b
2009-06-03 14:58:08 +0200 fs r272581 : #i102439#
2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls
2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font
2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary
2009-05-27 15:30:22 +0200 msc r272353 : #102303#
2009-05-26 13:03:06 +0200 fs r272295 : spelling
2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes
2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only
2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them
2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2
2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett
2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member
2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model
2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate
2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate
2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name
2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets
2009-05-20 11:29:55 +0200 msc r272111 : #i100000#
2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a
2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work
2009-05-20 09:43:36 +0200 oj r272106 : clean up includes
2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt
2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010#
2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey
2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset
2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column
2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names
2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date
2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date
2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019#
2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019#
2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010#
2009-05-15 10:21:24 +0200 msc r271929 : #101944#
2009-05-11 21:18:30 +0200 fs r271792 : #i99914#
2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span
2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode
2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue)
2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx
2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet
2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape
2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler
2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting
2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name
2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type
2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar
2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table
2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well
2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text
2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary
2009-05-07 11:47:18 +0200 fs r271647 : #i10000#
2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI
2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw
2009-05-07 10:09:55 +0200 fs r271634 : #i101623#
2009-05-07 09:53:44 +0200 fs r271631 : #i101622#
2009-05-06 21:55:53 +0200 fs r271615 : #i10000#
2009-05-06 21:10:42 +0200 fs r271611 : #i10000#
2009-05-06 13:11:48 +0200 fs r271583 : #i10000#
2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message
2009-05-05 22:29:03 +0200 fs r271558 : diagnostics
2009-05-05 22:16:16 +0200 fs r271557 : #i10000#
2009-05-05 13:50:32 +0200 fs r271513 : #i10000#
2009-05-05 10:21:50 +0200 fs r271503 : #i10000#
2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step?
2009-05-05 09:18:12 +0200 fs r271500 : #i10000#
2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47)
2009-05-04 14:51:26 +0200 fs r271456 : line ends
2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL
2009-04-22 21:18:34 +0200 fs r271141 : #i100944#
2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change
2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes
2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes
2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes
2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before
2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed
2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows
2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart
2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter
2009-04-17 21:00:23 +0200 fs r270954 : #i98350#
2009-04-17 13:54:19 +0200 fs r270942 : #i99565#
2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model
2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include
2009-04-17 10:10:15 +0200 fs r270926 : #i10000#
2009-04-17 10:02:36 +0200 fs r270925 : #i10000#
2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx
2009-04-16 21:05:25 +0200 fs r270903 : #i10000#
2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual
2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property
2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too
2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-15 14:53:13 +0200 fs r270844 : #i10000#
2009-04-15 13:08:29 +0200 fs r270836 : #i10000#
2009-04-15 12:28:14 +0200 fs r270832 : #i10000#
2009-04-15 10:59:14 +0200 fs r270827 : #i10000#
2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd
2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified
2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj
2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType
2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property
2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx
2009-04-14 15:46:54 +0200 fs r270784 : diagnostics
2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context
2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const
2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces
2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2
2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest
2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height
2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well
2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns
2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report
2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report
2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report
2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report
2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends
2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report
2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report
2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report
2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report
2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report
2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report
2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein
2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary
2009-04-03 14:35:49 +0200 fs r270487 : #i10000#
2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too
2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties
2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it
2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position
2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name
2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein
2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics
2009-04-02 16:35:19 +0200 fs r270421 : diagnostics
2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead
2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters
2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein
2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein
2009-04-02 14:10:35 +0200 fs r270405 : #i10000#
2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein
2009-04-02 14:03:03 +0200 fs r270401 : #i10000#
2009-04-02 13:58:13 +0200 fs r270400 : #i10000#
2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein
2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes
2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein
2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein
2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header
2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein
2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein
2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein
2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types
2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein
2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein
2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein
2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/>
2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used
2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode
2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein
2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge
2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein
2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein
2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table
2009-03-30 09:36:24 +0200 fs r270195 : assertion text
2009-03-28 20:21:58 +0100 fs r270187 : #ii10000#
2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids
2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids
2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset
2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45)
2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes
2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring
2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths
2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values
2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN
2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN
2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter
2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys
2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox
2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition
2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button
2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition
2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition
2009-03-25 10:29:07 +0100 fs r270003 : add missing localization
2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed
2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb
2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation
2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb
2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control
2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK
2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style
2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust
2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type
2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb
2009-03-20 08:52:47 +0100 fs r269780 : doc
2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different
2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider
2009-03-19 22:52:52 +0100 fs r269771 : added comment
2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration
2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now.
2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object
2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups
2009-03-19 09:25:27 +0100 fs r269727 : #i10000#
2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance
2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks
2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation
2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency
2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports
2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet)
2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work
2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation
2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext
2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long
2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null
2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params
2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment
2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed
2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment
2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle
2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups
2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList
2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface
2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList
2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups
2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups
2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion
2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode
2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode
2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes
2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long
2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents
2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive
2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header
2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type
2009-03-16 14:14:16 +0100 fs r269537 : line ends
2009-03-16 14:11:06 +0100 fs r269535 : line ends
2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter
2009-03-16 12:30:31 +0100 oj r269521 : compile error
2009-03-16 12:19:12 +0100 oj r269519 : compile error
2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap
2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43)
2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :)
2009-03-12 14:35:07 +0100 fs r269414 : not needed
2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module
2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib
2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure)
2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move
2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk
2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore
2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:45:07 +0100 fs r269401 : moved from ../
2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider
2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error
2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests
2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat
2009-03-12 12:34:53 +0100 fs r269388 : new API tests
2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed
2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring
2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop
2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider
2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop
2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications
2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications
2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications
2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components
2009-03-12 10:30:37 +0100 fs r269367 : module-local includes
2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata
2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name
2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty
2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language
2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer
2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map
2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer
2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied
2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed
2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults
2009-03-06 17:20:30 +0100 fs r269029 : #i98600#
2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ...
2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed
2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option
2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now
2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms
2009-03-06 09:53:41 +0100 fs r268977 : #i10000#
2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems
2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted)
2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20
2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages
2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42
2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings
2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups
2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b
2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b
2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData
2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations
2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL
2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types
2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator !=
2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size
2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now
2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric
2009-02-19 15:43:12 +0100 fs r268291 : #i99415#
2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account
2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title
2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
aInterestingProperties . push_back ( PROPERTY_TOGGLE ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
return Sequence < : : rtl : : OUString > ( & ( * aInterestingProperties . begin ( ) ) , aInterestingProperties . size ( ) ) ;
}
//--------------------------------------------------------------------
2006-07-26 06:56:33 +00:00
LineDescriptor SAL_CALL FormComponentPropertyHandler : : describePropertyLine ( const : : rtl : : OUString & _rPropertyName ,
const Reference < XPropertyControlFactory > & _rxControlFactory )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
throw ( UnknownPropertyException , NullPointerException , RuntimeException )
{
if ( ! _rxControlFactory . is ( ) )
throw NullPointerException ( ) ;
: : osl : : MutexGuard aGuard ( m_aMutex ) ;
PropertyId nPropId ( impl_getPropertyId_throw ( _rPropertyName ) ) ;
Property aProperty ( impl_getPropertyFromId_throw ( nPropId ) ) ;
//////////////////////////////////////////////////////////////////////
// for the MultiLine property, we have different UI translations depending on the control
// type
if ( nPropId = = PROPERTY_ID_MULTILINE )
{
if ( ( m_nClassId = = FormComponentType : : FIXEDTEXT )
| | ( m_nClassId = = FormComponentType : : COMMANDBUTTON )
| | ( m_nClassId = = FormComponentType : : RADIOBUTTON )
| | ( m_nClassId = = FormComponentType : : CHECKBOX )
)
nPropId = PROPERTY_ID_WORDBREAK ;
}
String sDisplayName = m_pInfoService - > getPropertyTranslation ( nPropId ) ;
if ( ! sDisplayName . Len ( ) )
{
DBG_ERROR ( " FormComponentPropertyHandler::describePropertyLine: did getSupportedProperties not work properly? " ) ;
throw UnknownPropertyException ( ) ;
}
//////////////////////////////////////////////////////////////////////
2006-07-26 06:56:33 +00:00
LineDescriptor aDescriptor ;
aDescriptor . HelpURL = HelpIdUrl : : getHelpURL ( m_pInfoService - > getPropertyHelpId ( nPropId ) ) ;
aDescriptor . DisplayName = sDisplayName ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
// for the moment, assume a text field
sal_Int16 nControlType = PropertyControlType : : TextField ;
sal_Bool bReadOnly = sal_False ;
2006-07-26 06:56:33 +00:00
aDescriptor . Control . clear ( ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
//////////////////////////////////////////////////////////////////////
bool bNeedDefaultStringIfVoidAllowed = false ;
TypeClass eType = aProperty . Type . getTypeClass ( ) ;
switch ( nPropId )
{
case PROPERTY_ID_DEFAULT_SELECT_SEQ :
case PROPERTY_ID_SELECTEDITEMS :
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_SELECTION ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
break ;
case PROPERTY_ID_FILTER :
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_FILTER ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
break ;
case PROPERTY_ID_SORT :
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_ORDER ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
break ;
case PROPERTY_ID_MASTERFIELDS :
case PROPERTY_ID_DETAILFIELDS :
nControlType = PropertyControlType : : StringListField ;
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_FORMLINKFIELDS ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
break ;
case PROPERTY_ID_COMMAND :
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_SQLCOMMAND ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
break ;
case PROPERTY_ID_TABINDEX :
{
Reference < XControlContainer > xControlContext ( impl_getContextControlContainer_nothrow ( ) ) ;
if ( xControlContext . is ( ) )
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_TABINDEX ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
nControlType = PropertyControlType : : NumericField ;
} ;
break ;
CWS-TOOLING: integrate CWS dba32b
2009-06-03 14:58:08 +0200 fs r272581 : #i102439#
2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls
2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font
2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary
2009-05-27 15:30:22 +0200 msc r272353 : #102303#
2009-05-26 13:03:06 +0200 fs r272295 : spelling
2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes
2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only
2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them
2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2
2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett
2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member
2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model
2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate
2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate
2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name
2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets
2009-05-20 11:29:55 +0200 msc r272111 : #i100000#
2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a
2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work
2009-05-20 09:43:36 +0200 oj r272106 : clean up includes
2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt
2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010#
2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey
2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset
2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column
2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names
2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date
2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date
2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019#
2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019#
2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010#
2009-05-15 10:21:24 +0200 msc r271929 : #101944#
2009-05-11 21:18:30 +0200 fs r271792 : #i99914#
2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span
2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode
2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue)
2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx
2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet
2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape
2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler
2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting
2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name
2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type
2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar
2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table
2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well
2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text
2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary
2009-05-07 11:47:18 +0200 fs r271647 : #i10000#
2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI
2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw
2009-05-07 10:09:55 +0200 fs r271634 : #i101623#
2009-05-07 09:53:44 +0200 fs r271631 : #i101622#
2009-05-06 21:55:53 +0200 fs r271615 : #i10000#
2009-05-06 21:10:42 +0200 fs r271611 : #i10000#
2009-05-06 13:11:48 +0200 fs r271583 : #i10000#
2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message
2009-05-05 22:29:03 +0200 fs r271558 : diagnostics
2009-05-05 22:16:16 +0200 fs r271557 : #i10000#
2009-05-05 13:50:32 +0200 fs r271513 : #i10000#
2009-05-05 10:21:50 +0200 fs r271503 : #i10000#
2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step?
2009-05-05 09:18:12 +0200 fs r271500 : #i10000#
2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47)
2009-05-04 14:51:26 +0200 fs r271456 : line ends
2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL
2009-04-22 21:18:34 +0200 fs r271141 : #i100944#
2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change
2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes
2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes
2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes
2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before
2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed
2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows
2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart
2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter
2009-04-17 21:00:23 +0200 fs r270954 : #i98350#
2009-04-17 13:54:19 +0200 fs r270942 : #i99565#
2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model
2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include
2009-04-17 10:10:15 +0200 fs r270926 : #i10000#
2009-04-17 10:02:36 +0200 fs r270925 : #i10000#
2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx
2009-04-16 21:05:25 +0200 fs r270903 : #i10000#
2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual
2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property
2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too
2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-15 14:53:13 +0200 fs r270844 : #i10000#
2009-04-15 13:08:29 +0200 fs r270836 : #i10000#
2009-04-15 12:28:14 +0200 fs r270832 : #i10000#
2009-04-15 10:59:14 +0200 fs r270827 : #i10000#
2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd
2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified
2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj
2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType
2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property
2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx
2009-04-14 15:46:54 +0200 fs r270784 : diagnostics
2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context
2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const
2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces
2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2
2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest
2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height
2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well
2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns
2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report
2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report
2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report
2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report
2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends
2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report
2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report
2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report
2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report
2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report
2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report
2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein
2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary
2009-04-03 14:35:49 +0200 fs r270487 : #i10000#
2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too
2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties
2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it
2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position
2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name
2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein
2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics
2009-04-02 16:35:19 +0200 fs r270421 : diagnostics
2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead
2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters
2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein
2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein
2009-04-02 14:10:35 +0200 fs r270405 : #i10000#
2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein
2009-04-02 14:03:03 +0200 fs r270401 : #i10000#
2009-04-02 13:58:13 +0200 fs r270400 : #i10000#
2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein
2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes
2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein
2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein
2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header
2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein
2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein
2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein
2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types
2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein
2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein
2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein
2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/>
2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used
2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode
2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein
2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge
2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein
2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein
2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table
2009-03-30 09:36:24 +0200 fs r270195 : assertion text
2009-03-28 20:21:58 +0100 fs r270187 : #ii10000#
2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids
2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids
2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset
2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45)
2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes
2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring
2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths
2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values
2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN
2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN
2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter
2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys
2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox
2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition
2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button
2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition
2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition
2009-03-25 10:29:07 +0100 fs r270003 : add missing localization
2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed
2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb
2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation
2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb
2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control
2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK
2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style
2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust
2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type
2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb
2009-03-20 08:52:47 +0100 fs r269780 : doc
2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different
2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider
2009-03-19 22:52:52 +0100 fs r269771 : added comment
2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration
2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now.
2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object
2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups
2009-03-19 09:25:27 +0100 fs r269727 : #i10000#
2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance
2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks
2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation
2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency
2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports
2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet)
2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work
2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation
2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext
2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long
2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null
2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params
2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment
2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed
2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment
2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle
2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups
2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList
2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface
2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList
2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups
2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups
2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion
2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode
2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode
2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes
2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long
2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents
2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive
2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header
2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type
2009-03-16 14:14:16 +0100 fs r269537 : line ends
2009-03-16 14:11:06 +0100 fs r269535 : line ends
2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter
2009-03-16 12:30:31 +0100 oj r269521 : compile error
2009-03-16 12:19:12 +0100 oj r269519 : compile error
2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap
2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43)
2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :)
2009-03-12 14:35:07 +0100 fs r269414 : not needed
2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module
2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib
2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure)
2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move
2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk
2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore
2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:45:07 +0100 fs r269401 : moved from ../
2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider
2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error
2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests
2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat
2009-03-12 12:34:53 +0100 fs r269388 : new API tests
2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed
2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring
2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop
2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider
2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop
2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications
2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications
2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications
2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components
2009-03-12 10:30:37 +0100 fs r269367 : module-local includes
2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata
2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name
2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty
2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language
2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer
2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map
2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer
2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied
2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed
2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults
2009-03-06 17:20:30 +0100 fs r269029 : #i98600#
2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ...
2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed
2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option
2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now
2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms
2009-03-06 09:53:41 +0100 fs r268977 : #i10000#
2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems
2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted)
2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20
2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages
2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42
2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings
2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups
2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b
2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b
2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData
2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations
2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL
2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types
2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator !=
2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size
2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now
2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric
2009-02-19 15:43:12 +0100 fs r268291 : #i99415#
2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account
2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title
2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
case PROPERTY_ID_FONT :
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
bReadOnly = sal_True ;
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_FONT_TYPE ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
break ;
case PROPERTY_ID_TARGET_URL :
case PROPERTY_ID_IMAGE_URL :
{
2006-07-26 06:56:33 +00:00
aDescriptor . Control = new OFileUrlControl ( impl_getDefaultDialogParent_nothrow ( ) , WB_TABSTOP | WB_BORDER ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = ( PROPERTY_ID_TARGET_URL = = nPropId )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
? UID_PROP_DLG_ATTR_TARGET_URL : UID_PROP_DLG_IMAGE_URL ;
}
break ;
case PROPERTY_ID_ECHO_CHAR :
nControlType = PropertyControlType : : CharacterField ;
break ;
case PROPERTY_ID_BACKGROUNDCOLOR :
case PROPERTY_ID_FILLCOLOR :
case PROPERTY_ID_SYMBOLCOLOR :
case PROPERTY_ID_BORDERCOLOR :
nControlType = PropertyControlType : : ColorListBox ;
switch ( nPropId )
{
case PROPERTY_ID_BACKGROUNDCOLOR :
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_BACKGROUNDCOLOR ; break ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_FILLCOLOR :
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_FILLCOLOR ; break ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_SYMBOLCOLOR :
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_SYMBOLCOLOR ; break ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_BORDERCOLOR :
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_BORDERCOLOR ; break ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
break ;
case PROPERTY_ID_LABEL :
nControlType = PropertyControlType : : MultiLineTextField ;
break ;
case PROPERTY_ID_DEFAULT_TEXT :
{
if ( FormComponentType : : FILECONTROL = = m_nClassId )
nControlType = PropertyControlType : : TextField ;
else
nControlType = PropertyControlType : : MultiLineTextField ;
}
break ;
case PROPERTY_ID_TEXT :
if ( impl_componentHasProperty_throw ( PROPERTY_MULTILINE ) )
nControlType = PropertyControlType : : MultiLineTextField ;
break ;
case PROPERTY_ID_CONTROLLABEL :
bReadOnly = sal_True ;
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_CONTROLLABEL ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
break ;
case PROPERTY_ID_FORMATKEY :
case PROPERTY_ID_EFFECTIVE_MIN :
case PROPERTY_ID_EFFECTIVE_MAX :
case PROPERTY_ID_EFFECTIVE_DEFAULT :
case PROPERTY_ID_EFFECTIVE_VALUE :
{
// and the supplier is really available
Reference < XNumberFormatsSupplier > xSupplier ;
m_xComponent - > getPropertyValue ( PROPERTY_FORMATSSUPPLIER ) > > = xSupplier ;
if ( xSupplier . is ( ) )
{
Reference < XUnoTunnel > xTunnel ( xSupplier , UNO_QUERY ) ;
DBG_ASSERT ( xTunnel . is ( ) , " FormComponentPropertyHandler::describePropertyLine : xTunnel is invalid! " ) ;
2007-07-06 07:48:27 +00:00
SvNumberFormatsSupplierObj * pSupplier = reinterpret_cast < SvNumberFormatsSupplierObj * > ( xTunnel - > getSomething ( SvNumberFormatsSupplierObj : : getUnoTunnelId ( ) ) ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( pSupplier ! = NULL )
{
sal_Bool bIsFormatKey = ( PROPERTY_ID_FORMATKEY = = nPropId ) ;
bReadOnly = bIsFormatKey ;
if ( bIsFormatKey )
{
OFormatSampleControl * pControl = new OFormatSampleControl ( impl_getDefaultDialogParent_nothrow ( ) , WB_READONLY | WB_TABSTOP | WB_BORDER ) ;
2006-07-26 06:56:33 +00:00
aDescriptor . Control = pControl ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
pControl - > SetFormatSupplier ( pSupplier ) ;
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_NUMBER_FORMAT ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
else
{
OFormattedNumericControl * pControl = new OFormattedNumericControl ( impl_getDefaultDialogParent_nothrow ( ) , WB_TABSTOP | WB_BORDER ) ;
2006-07-26 06:56:33 +00:00
aDescriptor . Control = pControl ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
FormatDescription aDesc ;
aDesc . pSupplier = pSupplier ;
Any aFormatKeyValue = m_xComponent - > getPropertyValue ( PROPERTY_FORMATKEY ) ;
if ( ! ( aFormatKeyValue > > = aDesc . nKey ) )
aDesc . nKey = 0 ;
pControl - > SetFormatDescription ( aDesc ) ;
}
}
}
}
break ;
case PROPERTY_ID_DATEMIN :
case PROPERTY_ID_DATEMAX :
case PROPERTY_ID_DEFAULT_DATE :
case PROPERTY_ID_DATE :
nControlType = PropertyControlType : : DateField ;
break ;
case PROPERTY_ID_TIMEMIN :
case PROPERTY_ID_TIMEMAX :
case PROPERTY_ID_DEFAULT_TIME :
case PROPERTY_ID_TIME :
nControlType = PropertyControlType : : TimeField ;
break ;
case PROPERTY_ID_VALUEMIN :
case PROPERTY_ID_VALUEMAX :
case PROPERTY_ID_DEFAULT_VALUE :
case PROPERTY_ID_VALUE :
{
OFormattedNumericControl * pControl = new OFormattedNumericControl ( impl_getDefaultDialogParent_nothrow ( ) , WB_TABSTOP | WB_BORDER | WB_SPIN | WB_REPEAT ) ;
2006-07-26 06:56:33 +00:00
aDescriptor . Control = pControl ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
// we don't set a formatter so the control uses a default (which uses the application
// language and a default numeric format)
// but we set the decimal digits
pControl - > SetDecimalDigits (
: : comphelper : : getINT16 ( m_xComponent - > getPropertyValue ( PROPERTY_DECIMAL_ACCURACY ) )
) ;
// and the thousands separator
pControl - > SetThousandsSep (
: : comphelper : : getBOOL ( m_xComponent - > getPropertyValue ( PROPERTY_SHOWTHOUSANDSEP ) )
) ;
// and the default value for the property
try
{
if ( m_xPropertyState . is ( ) & & ( ( PROPERTY_ID_VALUEMIN = = nPropId ) | | ( PROPERTY_ID_VALUEMAX = = nPropId ) ) )
{
double nDefault = 0 ;
if ( m_xPropertyState - > getPropertyDefault ( aProperty . Name ) > > = nDefault )
pControl - > SetDefaultValue ( nDefault ) ;
}
}
catch ( Exception & )
{
// just ignore it
}
// and allow empty values only for the default value and the value
pControl - > EnableEmptyField ( ( PROPERTY_ID_DEFAULT_VALUE = = nPropId )
| | ( PROPERTY_ID_VALUE = = nPropId ) ) ;
}
break ;
default :
if ( TypeClass_BYTE < = eType & & eType < = TypeClass_DOUBLE )
{
sal_Int16 nDigits = 0 ;
sal_Int16 nValueUnit = - 1 ;
sal_Int16 nDisplayUnit = - 1 ;
if ( m_eComponentClass = = eFormControl )
{
if ( ( nPropId = = PROPERTY_ID_WIDTH )
| | ( nPropId = = PROPERTY_ID_ROWHEIGHT )
2007-07-06 07:48:27 +00:00
| | ( nPropId = = PROPERTY_ID_HEIGHT )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
)
{
nValueUnit = MeasureUnit : : MM_10TH ;
nDisplayUnit = impl_getDocumentMeasurementUnit_throw ( ) ;
nDigits = 2 ;
}
}
Optional < double > aValueNotPresent ( sal_False , 0 ) ;
2006-07-26 06:56:33 +00:00
aDescriptor . Control = PropertyHandlerHelper : : createNumericControl (
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
_rxControlFactory , nDigits , aValueNotPresent , aValueNotPresent , sal_False ) ;
2006-07-26 06:56:33 +00:00
Reference < XNumericControl > xNumericControl ( aDescriptor . Control , UNO_QUERY_THROW ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( nValueUnit ! = - 1 )
xNumericControl - > setValueUnit ( nValueUnit ) ;
if ( nDisplayUnit ! = - 1 )
xNumericControl - > setDisplayUnit ( nDisplayUnit ) ;
}
break ;
}
//////////////////////////////////////////////////////////////////////
if ( eType = = TypeClass_SEQUENCE )
nControlType = PropertyControlType : : StringListField ;
//////////////////////////////////////////////////////////////////////
// boolean values
if ( eType = = TypeClass_BOOLEAN )
{
2008-12-10 13:41:25 +00:00
USHORT nResId = RID_RSC_ENUM_YESNO ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( ( nPropId = = PROPERTY_ID_SHOW_POSITION )
| | ( nPropId = = PROPERTY_ID_SHOW_NAVIGATION )
| | ( nPropId = = PROPERTY_ID_SHOW_RECORDACTIONS )
| | ( nPropId = = PROPERTY_ID_SHOW_FILTERSORT )
)
2008-12-10 13:41:25 +00:00
nResId = RID_RSC_ENUM_SHOWHIDE ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
: : std : : vector < : : rtl : : OUString > aListEntries ;
2008-12-10 13:41:25 +00:00
tools : : StringListResource aRes ( PcrRes ( nResId ) , aListEntries ) ;
2006-12-13 15:57:02 +00:00
aDescriptor . Control = PropertyHandlerHelper : : createListBoxControl ( _rxControlFactory , aListEntries , sal_False , sal_False ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
bNeedDefaultStringIfVoidAllowed = true ;
}
//////////////////////////////////////////////////////////////////////
// enum properties
sal_uInt32 nPropertyUIFlags = m_pInfoService - > getPropertyUIFlags ( nPropId ) ;
bool bIsEnumProperty = ( nPropertyUIFlags & PROP_FLAG_ENUM ) ! = 0 ;
if ( bIsEnumProperty | | ( PROPERTY_ID_TARGET_FRAME = = nPropId ) )
{
: : std : : vector < : : rtl : : OUString > aEnumValues = m_pInfoService - > getPropertyEnumRepresentations ( nPropId ) ;
: : std : : vector < : : rtl : : OUString > : : const_iterator pStart = aEnumValues . begin ( ) ;
: : std : : vector < : : rtl : : OUString > : : const_iterator pEnd = aEnumValues . end ( ) ;
// for a checkbox: if "ambiguous" is not allowed, remove this from the sequence
CWS-TOOLING: integrate CWS dba32b
2009-06-03 14:58:08 +0200 fs r272581 : #i102439#
2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls
2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font
2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary
2009-05-27 15:30:22 +0200 msc r272353 : #102303#
2009-05-26 13:03:06 +0200 fs r272295 : spelling
2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes
2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only
2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them
2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2
2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett
2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member
2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model
2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate
2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate
2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name
2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets
2009-05-20 11:29:55 +0200 msc r272111 : #i100000#
2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a
2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work
2009-05-20 09:43:36 +0200 oj r272106 : clean up includes
2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt
2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010#
2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey
2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset
2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column
2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names
2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date
2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date
2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019#
2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019#
2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010#
2009-05-15 10:21:24 +0200 msc r271929 : #101944#
2009-05-11 21:18:30 +0200 fs r271792 : #i99914#
2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span
2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode
2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue)
2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx
2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet
2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape
2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler
2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting
2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name
2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type
2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar
2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table
2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well
2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text
2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary
2009-05-07 11:47:18 +0200 fs r271647 : #i10000#
2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI
2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw
2009-05-07 10:09:55 +0200 fs r271634 : #i101623#
2009-05-07 09:53:44 +0200 fs r271631 : #i101622#
2009-05-06 21:55:53 +0200 fs r271615 : #i10000#
2009-05-06 21:10:42 +0200 fs r271611 : #i10000#
2009-05-06 13:11:48 +0200 fs r271583 : #i10000#
2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message
2009-05-05 22:29:03 +0200 fs r271558 : diagnostics
2009-05-05 22:16:16 +0200 fs r271557 : #i10000#
2009-05-05 13:50:32 +0200 fs r271513 : #i10000#
2009-05-05 10:21:50 +0200 fs r271503 : #i10000#
2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step?
2009-05-05 09:18:12 +0200 fs r271500 : #i10000#
2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47)
2009-05-04 14:51:26 +0200 fs r271456 : line ends
2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL
2009-04-22 21:18:34 +0200 fs r271141 : #i100944#
2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change
2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes
2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes
2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes
2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before
2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed
2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows
2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart
2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter
2009-04-17 21:00:23 +0200 fs r270954 : #i98350#
2009-04-17 13:54:19 +0200 fs r270942 : #i99565#
2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model
2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include
2009-04-17 10:10:15 +0200 fs r270926 : #i10000#
2009-04-17 10:02:36 +0200 fs r270925 : #i10000#
2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx
2009-04-16 21:05:25 +0200 fs r270903 : #i10000#
2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual
2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property
2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too
2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-15 14:53:13 +0200 fs r270844 : #i10000#
2009-04-15 13:08:29 +0200 fs r270836 : #i10000#
2009-04-15 12:28:14 +0200 fs r270832 : #i10000#
2009-04-15 10:59:14 +0200 fs r270827 : #i10000#
2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd
2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified
2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj
2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType
2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property
2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx
2009-04-14 15:46:54 +0200 fs r270784 : diagnostics
2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context
2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const
2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces
2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2
2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest
2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height
2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well
2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns
2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report
2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report
2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report
2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report
2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends
2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report
2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report
2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report
2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report
2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report
2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report
2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein
2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary
2009-04-03 14:35:49 +0200 fs r270487 : #i10000#
2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too
2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties
2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it
2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position
2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name
2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein
2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics
2009-04-02 16:35:19 +0200 fs r270421 : diagnostics
2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead
2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters
2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein
2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein
2009-04-02 14:10:35 +0200 fs r270405 : #i10000#
2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein
2009-04-02 14:03:03 +0200 fs r270401 : #i10000#
2009-04-02 13:58:13 +0200 fs r270400 : #i10000#
2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein
2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes
2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein
2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein
2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header
2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein
2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein
2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein
2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types
2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein
2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein
2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein
2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/>
2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used
2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode
2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein
2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge
2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein
2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein
2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table
2009-03-30 09:36:24 +0200 fs r270195 : assertion text
2009-03-28 20:21:58 +0100 fs r270187 : #ii10000#
2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids
2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids
2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset
2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45)
2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes
2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring
2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths
2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values
2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN
2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN
2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter
2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys
2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox
2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition
2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button
2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition
2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition
2009-03-25 10:29:07 +0100 fs r270003 : add missing localization
2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed
2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb
2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation
2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb
2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control
2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK
2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style
2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust
2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type
2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb
2009-03-20 08:52:47 +0100 fs r269780 : doc
2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different
2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider
2009-03-19 22:52:52 +0100 fs r269771 : added comment
2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration
2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now.
2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object
2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups
2009-03-19 09:25:27 +0100 fs r269727 : #i10000#
2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance
2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks
2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation
2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency
2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports
2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet)
2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work
2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation
2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext
2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long
2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null
2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params
2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment
2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed
2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment
2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle
2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups
2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList
2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface
2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList
2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups
2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups
2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion
2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode
2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode
2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes
2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long
2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents
2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive
2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header
2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type
2009-03-16 14:14:16 +0100 fs r269537 : line ends
2009-03-16 14:11:06 +0100 fs r269535 : line ends
2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter
2009-03-16 12:30:31 +0100 oj r269521 : compile error
2009-03-16 12:19:12 +0100 oj r269519 : compile error
2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap
2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43)
2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :)
2009-03-12 14:35:07 +0100 fs r269414 : not needed
2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module
2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib
2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure)
2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move
2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk
2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore
2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:45:07 +0100 fs r269401 : moved from ../
2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider
2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error
2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests
2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat
2009-03-12 12:34:53 +0100 fs r269388 : new API tests
2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed
2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring
2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop
2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider
2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop
2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications
2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications
2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications
2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components
2009-03-12 10:30:37 +0100 fs r269367 : module-local includes
2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata
2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name
2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty
2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language
2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer
2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map
2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer
2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied
2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed
2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults
2009-03-06 17:20:30 +0100 fs r269029 : #i98600#
2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ...
2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed
2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option
2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now
2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms
2009-03-06 09:53:41 +0100 fs r268977 : #i10000#
2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems
2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted)
2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20
2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages
2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42
2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings
2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups
2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b
2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b
2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData
2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations
2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL
2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types
2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator !=
2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size
2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now
2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric
2009-02-19 15:43:12 +0100 fs r268291 : #i99415#
2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account
2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title
2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
if ( ( PROPERTY_ID_DEFAULT_STATE = = nPropId )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
| | ( PROPERTY_ID_STATE = = nPropId )
)
2008-12-11 07:05:03 +00:00
{
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( impl_componentHasProperty_throw ( PROPERTY_TRISTATE ) )
{
if ( ! : : comphelper : : getBOOL ( m_xComponent - > getPropertyValue ( PROPERTY_TRISTATE ) ) )
{ // remove the last sequence element
if ( pEnd > pStart )
- - pEnd ;
}
}
else
- - pEnd ;
2008-12-11 07:05:03 +00:00
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( PROPERTY_ID_LISTSOURCETYPE = = nPropId )
if ( FormComponentType : : COMBOBOX = = m_nClassId )
// remove the first sequence element -> value list not possible for combo boxes
+ + pStart ;
// copy the sequence
: : std : : vector < : : rtl : : OUString > aListEntries ( pEnd - pStart ) ;
: : std : : copy ( pStart , pEnd , aListEntries . begin ( ) ) ;
// create the control
if ( PROPERTY_ID_TARGET_FRAME = = nPropId )
2006-12-13 15:57:02 +00:00
aDescriptor . Control = PropertyHandlerHelper : : createComboBoxControl ( _rxControlFactory , aListEntries , sal_False , sal_False ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
else
{
2006-12-13 15:57:02 +00:00
aDescriptor . Control = PropertyHandlerHelper : : createListBoxControl ( _rxControlFactory , aListEntries , sal_False , sal_False ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
bNeedDefaultStringIfVoidAllowed = true ;
}
}
//////////////////////////////////////////////////////////////////////
switch ( nPropId )
{
case PROPERTY_ID_REPEAT_DELAY :
{
OTimeDurationControl * pControl = new OTimeDurationControl ( impl_getDefaultDialogParent_nothrow ( ) , WB_BORDER | WB_TABSTOP ) ;
2006-07-26 06:56:33 +00:00
aDescriptor . Control = pControl ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
pControl - > setMinValue ( Optional < double > ( sal_True , 0 ) ) ;
pControl - > setMaxValue ( Optional < double > ( sal_True , : : std : : numeric_limits < double > : : max ( ) ) ) ;
}
break ;
case PROPERTY_ID_TABINDEX :
case PROPERTY_ID_BOUNDCOLUMN :
case PROPERTY_ID_VISIBLESIZE :
case PROPERTY_ID_MAXTEXTLEN :
case PROPERTY_ID_LINEINCREMENT :
case PROPERTY_ID_BLOCKINCREMENT :
case PROPERTY_ID_SPININCREMENT :
{
Optional < double > aMinValue ( sal_True , 0 ) ;
Optional < double > aMaxValue ( sal_True , 0x7FFFFFFF ) ;
if ( nPropId = = PROPERTY_ID_MAXTEXTLEN )
aMinValue . Value = - 1 ;
else if ( ( nPropId = = PROPERTY_ID_BOUNDCOLUMN ) | | ( nPropId = = PROPERTY_ID_VISIBLESIZE ) )
aMinValue . Value = 1 ;
else
aMinValue . Value = 0 ;
2006-07-26 06:56:33 +00:00
aDescriptor . Control = PropertyHandlerHelper : : createNumericControl (
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
_rxControlFactory , 0 , aMinValue , aMaxValue , sal_False ) ;
}
break ;
case PROPERTY_ID_DECIMAL_ACCURACY :
{
Optional < double > aMinValue ( sal_True , 0 ) ;
Optional < double > aMaxValue ( sal_True , 20 ) ;
2006-07-26 06:56:33 +00:00
aDescriptor . Control = PropertyHandlerHelper : : createNumericControl (
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
_rxControlFactory , 0 , aMinValue , aMaxValue , sal_False ) ;
}
break ;
//////////////////////////////////////////////////////////////////////
// DataSource
case PROPERTY_ID_DATASOURCE :
{
2006-07-26 06:56:33 +00:00
aDescriptor . PrimaryButtonId = UID_PROP_DLG_ATTR_DATASOURCE ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
: : std : : vector < : : rtl : : OUString > aListEntries ;
Reference < XNameAccess > xDatabaseContext ;
m_aContext . createComponent ( ( rtl : : OUString ) SERVICE_DATABASE_CONTEXT , xDatabaseContext ) ;
if ( xDatabaseContext . is ( ) )
{
Sequence < : : rtl : : OUString > aDatasources = xDatabaseContext - > getElementNames ( ) ;
aListEntries . resize ( aDatasources . getLength ( ) ) ;
: : std : : copy ( aDatasources . getConstArray ( ) , aDatasources . getConstArray ( ) + aDatasources . getLength ( ) ,
aListEntries . begin ( ) ) ;
}
2006-07-26 06:56:33 +00:00
aDescriptor . Control = PropertyHandlerHelper : : createComboBoxControl (
2006-12-13 15:57:02 +00:00
_rxControlFactory , aListEntries , sal_False , sal_True ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
break ;
case PROPERTY_ID_CONTROLSOURCE :
{
: : std : : vector < : : rtl : : OUString > aFieldNames ;
impl_initFieldList_nothrow ( aFieldNames ) ;
2006-07-26 06:56:33 +00:00
aDescriptor . Control = PropertyHandlerHelper : : createComboBoxControl (
2006-12-13 15:57:02 +00:00
_rxControlFactory , aFieldNames , sal_False , sal_False ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
break ;
case PROPERTY_ID_COMMAND :
2006-07-26 06:56:33 +00:00
impl_describeCursorSource_nothrow ( aDescriptor , _rxControlFactory ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
break ;
case PROPERTY_ID_LISTSOURCE :
2006-07-26 06:56:33 +00:00
impl_describeListSourceUI_throw ( aDescriptor , _rxControlFactory ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
break ;
}
2006-07-26 06:56:33 +00:00
if ( ! aDescriptor . Control . is ( ) )
aDescriptor . Control = _rxControlFactory - > createPropertyControl ( nControlType , bReadOnly ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( ( aProperty . Attributes & PropertyAttribute : : MAYBEVOID ) ! = 0 )
{
// insert the string "Default" string, if necessary
if ( bNeedDefaultStringIfVoidAllowed | | ( nControlType = = PropertyControlType : : ColorListBox ) )
{
2006-07-26 06:56:33 +00:00
Reference < XStringListControl > xStringList ( aDescriptor . Control , UNO_QUERY_THROW ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
xStringList - > prependListEntry ( m_sDefaultValueString ) ;
m_aPropertiesWithDefListEntry . insert ( _rPropertyName ) ;
}
}
2006-07-26 06:56:33 +00:00
if ( aDescriptor . PrimaryButtonId )
aDescriptor . HasPrimaryButton = sal_True ;
if ( aDescriptor . SecondaryButtonId )
aDescriptor . HasSecondaryButton = sal_True ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
bool bIsDataProperty = ( nPropertyUIFlags & PROP_FLAG_DATA_PROPERTY ) ! = 0 ;
2006-07-26 06:56:33 +00:00
aDescriptor . Category = : : rtl : : OUString : : createFromAscii ( bIsDataProperty ? " Data " : " General " ) ;
return aDescriptor ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
//--------------------------------------------------------------------
2006-07-26 06:56:33 +00:00
InteractiveSelectionResult SAL_CALL FormComponentPropertyHandler : : onInteractivePropertySelection ( const : : rtl : : OUString & _rPropertyName , sal_Bool /*_bPrimary*/ , Any & _rData , const Reference < XObjectInspectorUI > & _rxInspectorUI ) throw ( UnknownPropertyException , NullPointerException , RuntimeException )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
if ( ! _rxInspectorUI . is ( ) )
throw NullPointerException ( ) ;
: : osl : : ClearableMutexGuard aGuard ( m_aMutex ) ;
PropertyId nPropId ( impl_getPropertyId_throw ( _rPropertyName ) ) ;
InteractiveSelectionResult eResult = InteractiveSelectionResult_Cancelled ;
switch ( nPropId )
{
case PROPERTY_ID_DEFAULT_SELECT_SEQ :
case PROPERTY_ID_SELECTEDITEMS :
if ( impl_dialogListSelection_nothrow ( _rPropertyName , aGuard ) )
eResult = InteractiveSelectionResult_Success ;
break ;
case PROPERTY_ID_FILTER :
case PROPERTY_ID_SORT :
{
: : rtl : : OUString sClause ;
if ( impl_dialogFilterOrSort_nothrow ( PROPERTY_ID_FILTER = = nPropId , sClause , aGuard ) )
{
_rData < < = sClause ;
eResult = InteractiveSelectionResult_ObtainedValue ;
}
}
break ;
case PROPERTY_ID_MASTERFIELDS :
case PROPERTY_ID_DETAILFIELDS :
if ( impl_dialogLinkedFormFields_nothrow ( aGuard ) )
eResult = InteractiveSelectionResult_Success ;
break ;
case PROPERTY_ID_FORMATKEY :
if ( impl_dialogFormatting_nothrow ( _rData , aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue ;
break ;
case PROPERTY_ID_IMAGE_URL :
if ( impl_browseForImage_nothrow ( _rData , aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue ;
break ;
case PROPERTY_ID_TARGET_URL :
if ( impl_browseForTargetURL_nothrow ( _rData , aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue ;
break ;
CWS-TOOLING: integrate CWS dba32b
2009-06-03 14:58:08 +0200 fs r272581 : #i102439#
2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls
2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font
2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary
2009-05-27 15:30:22 +0200 msc r272353 : #102303#
2009-05-26 13:03:06 +0200 fs r272295 : spelling
2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes
2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only
2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them
2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2
2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett
2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member
2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model
2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate
2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate
2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name
2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets
2009-05-20 11:29:55 +0200 msc r272111 : #i100000#
2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a
2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work
2009-05-20 09:43:36 +0200 oj r272106 : clean up includes
2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt
2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010#
2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey
2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset
2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column
2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names
2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date
2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date
2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019#
2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019#
2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010#
2009-05-15 10:21:24 +0200 msc r271929 : #101944#
2009-05-11 21:18:30 +0200 fs r271792 : #i99914#
2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span
2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode
2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue)
2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx
2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet
2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape
2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler
2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting
2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name
2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type
2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar
2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table
2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well
2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text
2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary
2009-05-07 11:47:18 +0200 fs r271647 : #i10000#
2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI
2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw
2009-05-07 10:09:55 +0200 fs r271634 : #i101623#
2009-05-07 09:53:44 +0200 fs r271631 : #i101622#
2009-05-06 21:55:53 +0200 fs r271615 : #i10000#
2009-05-06 21:10:42 +0200 fs r271611 : #i10000#
2009-05-06 13:11:48 +0200 fs r271583 : #i10000#
2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message
2009-05-05 22:29:03 +0200 fs r271558 : diagnostics
2009-05-05 22:16:16 +0200 fs r271557 : #i10000#
2009-05-05 13:50:32 +0200 fs r271513 : #i10000#
2009-05-05 10:21:50 +0200 fs r271503 : #i10000#
2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step?
2009-05-05 09:18:12 +0200 fs r271500 : #i10000#
2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47)
2009-05-04 14:51:26 +0200 fs r271456 : line ends
2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL
2009-04-22 21:18:34 +0200 fs r271141 : #i100944#
2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change
2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes
2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes
2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes
2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before
2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed
2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows
2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart
2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter
2009-04-17 21:00:23 +0200 fs r270954 : #i98350#
2009-04-17 13:54:19 +0200 fs r270942 : #i99565#
2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model
2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include
2009-04-17 10:10:15 +0200 fs r270926 : #i10000#
2009-04-17 10:02:36 +0200 fs r270925 : #i10000#
2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx
2009-04-16 21:05:25 +0200 fs r270903 : #i10000#
2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual
2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property
2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too
2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-15 14:53:13 +0200 fs r270844 : #i10000#
2009-04-15 13:08:29 +0200 fs r270836 : #i10000#
2009-04-15 12:28:14 +0200 fs r270832 : #i10000#
2009-04-15 10:59:14 +0200 fs r270827 : #i10000#
2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd
2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified
2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj
2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType
2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property
2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx
2009-04-14 15:46:54 +0200 fs r270784 : diagnostics
2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context
2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const
2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces
2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2
2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest
2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height
2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well
2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns
2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report
2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report
2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report
2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report
2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends
2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report
2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report
2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report
2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report
2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report
2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report
2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein
2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary
2009-04-03 14:35:49 +0200 fs r270487 : #i10000#
2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too
2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties
2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it
2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position
2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name
2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein
2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics
2009-04-02 16:35:19 +0200 fs r270421 : diagnostics
2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead
2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters
2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein
2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein
2009-04-02 14:10:35 +0200 fs r270405 : #i10000#
2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein
2009-04-02 14:03:03 +0200 fs r270401 : #i10000#
2009-04-02 13:58:13 +0200 fs r270400 : #i10000#
2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein
2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes
2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein
2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein
2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header
2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein
2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein
2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein
2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types
2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein
2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein
2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein
2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/>
2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used
2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode
2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein
2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge
2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein
2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein
2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table
2009-03-30 09:36:24 +0200 fs r270195 : assertion text
2009-03-28 20:21:58 +0100 fs r270187 : #ii10000#
2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids
2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids
2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset
2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45)
2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes
2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring
2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths
2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values
2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN
2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN
2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter
2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys
2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox
2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition
2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button
2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition
2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition
2009-03-25 10:29:07 +0100 fs r270003 : add missing localization
2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed
2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb
2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation
2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb
2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control
2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK
2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style
2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust
2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type
2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb
2009-03-20 08:52:47 +0100 fs r269780 : doc
2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different
2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider
2009-03-19 22:52:52 +0100 fs r269771 : added comment
2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration
2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now.
2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object
2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups
2009-03-19 09:25:27 +0100 fs r269727 : #i10000#
2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance
2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks
2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation
2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency
2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports
2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet)
2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work
2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation
2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext
2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long
2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null
2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params
2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment
2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed
2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment
2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle
2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups
2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList
2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface
2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList
2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups
2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups
2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion
2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode
2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode
2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes
2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long
2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents
2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive
2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header
2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type
2009-03-16 14:14:16 +0100 fs r269537 : line ends
2009-03-16 14:11:06 +0100 fs r269535 : line ends
2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter
2009-03-16 12:30:31 +0100 oj r269521 : compile error
2009-03-16 12:19:12 +0100 oj r269519 : compile error
2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap
2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43)
2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :)
2009-03-12 14:35:07 +0100 fs r269414 : not needed
2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module
2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib
2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure)
2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move
2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk
2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore
2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:45:07 +0100 fs r269401 : moved from ../
2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider
2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error
2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests
2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat
2009-03-12 12:34:53 +0100 fs r269388 : new API tests
2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed
2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring
2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop
2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider
2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop
2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications
2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications
2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications
2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components
2009-03-12 10:30:37 +0100 fs r269367 : module-local includes
2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata
2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name
2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty
2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language
2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer
2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map
2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer
2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied
2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed
2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults
2009-03-06 17:20:30 +0100 fs r269029 : #i98600#
2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ...
2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed
2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option
2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now
2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms
2009-03-06 09:53:41 +0100 fs r268977 : #i10000#
2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems
2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted)
2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20
2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages
2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42
2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings
2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups
2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b
2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b
2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData
2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations
2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL
2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types
2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator !=
2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size
2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now
2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric
2009-02-19 15:43:12 +0100 fs r268291 : #i99415#
2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account
2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title
2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
case PROPERTY_ID_FONT :
2006-03-31 11:19:30 +00:00
if ( impl_executeFontDialog_nothrow ( _rData , aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
break ;
case PROPERTY_ID_DATASOURCE :
if ( impl_browseForDatabaseDocument_throw ( _rData , aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue ;
break ;
case PROPERTY_ID_BACKGROUNDCOLOR :
case PROPERTY_ID_FILLCOLOR :
case PROPERTY_ID_SYMBOLCOLOR :
case PROPERTY_ID_BORDERCOLOR :
if ( impl_dialogColorChooser_throw ( nPropId , _rData , aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue ;
break ;
case PROPERTY_ID_CONTROLLABEL :
if ( impl_dialogChooseLabelControl_nothrow ( _rData , aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue ;
break ;
case PROPERTY_ID_TABINDEX :
if ( impl_dialogChangeTabOrder_nothrow ( aGuard ) )
eResult = InteractiveSelectionResult_Success ;
break ;
case PROPERTY_ID_COMMAND :
2007-11-21 15:21:57 +00:00
case PROPERTY_ID_LISTSOURCE :
if ( impl_doDesignSQLCommand_nothrow ( _rxInspectorUI , nPropId ) )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
eResult = InteractiveSelectionResult_Pending ;
break ;
default :
DBG_ERROR ( " FormComponentPropertyHandler::onInteractivePropertySelection: request for a property which does not have dedicated UI! " ) ;
break ;
}
return eResult ;
}
//--------------------------------------------------------------------
namespace
{
void lcl_rebuildAndResetCommand ( const Reference < XObjectInspectorUI > & _rxInspectorUI , const Reference < XPropertyHandler > & _rxHandler )
{
OSL_PRECOND ( _rxInspectorUI . is ( ) , " lcl_rebuildAndResetCommand: invalid BrowserUI! " ) ;
OSL_PRECOND ( _rxHandler . is ( ) , " lcl_rebuildAndResetCommand: invalid handler! " ) ;
_rxInspectorUI - > rebuildPropertyUI ( PROPERTY_COMMAND ) ;
_rxHandler - > setPropertyValue ( PROPERTY_COMMAND , makeAny ( : : rtl : : OUString ( ) ) ) ;
}
}
//--------------------------------------------------------------------
2006-07-26 06:56:33 +00:00
void SAL_CALL FormComponentPropertyHandler : : actuatingPropertyChanged ( const : : rtl : : OUString & _rActuatingPropertyName , const Any & _rNewValue , const Any & /*_rOldValue*/ , const Reference < XObjectInspectorUI > & _rxInspectorUI , sal_Bool _bFirstTimeInit ) throw ( NullPointerException , RuntimeException )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
if ( ! _rxInspectorUI . is ( ) )
throw NullPointerException ( ) ;
: : osl : : MutexGuard aGuard ( m_aMutex ) ;
PropertyId nActuatingPropId ( impl_getPropertyId_throw ( _rActuatingPropertyName ) ) ;
: : std : : vector < PropertyId > aDependentProperties ;
switch ( nActuatingPropId )
{
// ----- EscapeProcessing -----
case PROPERTY_ID_ESCAPE_PROCESSING :
aDependentProperties . push_back ( PROPERTY_ID_FILTER ) ;
aDependentProperties . push_back ( PROPERTY_ID_SORT ) ;
break ; // case PROPERTY_ID_ESCAPE_PROCESSING
// ----- CommandType -----
case PROPERTY_ID_COMMANDTYPE :
// available commands (tables or queries) might have changed
if ( ! _bFirstTimeInit & & m_bHaveCommand )
lcl_rebuildAndResetCommand ( _rxInspectorUI , this ) ;
aDependentProperties . push_back ( PROPERTY_ID_COMMAND ) ;
break ; // case PROPERTY_ID_COMMANDTYPE
// ----- DataSourceName -----
case PROPERTY_ID_DATASOURCE :
// reset the connection, now that we have a new data source
impl_clearRowsetConnection_nothrow ( ) ;
// available list source values (tables or queries) might have changed
if ( ! _bFirstTimeInit & & m_bHaveListSource )
_rxInspectorUI - > rebuildPropertyUI ( PROPERTY_LISTSOURCE ) ;
// available commands (tables or queries) might have changed
if ( ! _bFirstTimeInit & & m_bHaveCommand )
lcl_rebuildAndResetCommand ( _rxInspectorUI , this ) ;
// Command also depends on DataSource
aDependentProperties . push_back ( PROPERTY_ID_COMMAND ) ;
// NO break!
// ----- Command -----
case PROPERTY_ID_COMMAND :
aDependentProperties . push_back ( PROPERTY_ID_FILTER ) ;
aDependentProperties . push_back ( PROPERTY_ID_SORT ) ;
if ( m_bComponentIsSubForm )
aDependentProperties . push_back ( PROPERTY_ID_DETAILFIELDS ) ;
break ;
// ----- ListSourceType -----
case PROPERTY_ID_LISTSOURCETYPE :
if ( ! _bFirstTimeInit & & m_bHaveListSource )
// available list source values (tables or queries) might have changed
_rxInspectorUI - > rebuildPropertyUI ( PROPERTY_LISTSOURCE ) ;
aDependentProperties . push_back ( PROPERTY_ID_BOUNDCOLUMN ) ;
aDependentProperties . push_back ( PROPERTY_ID_STRINGITEMLIST ) ;
// NO break!
// ----- StringItemList -----
case PROPERTY_ID_STRINGITEMLIST :
aDependentProperties . push_back ( PROPERTY_ID_SELECTEDITEMS ) ;
aDependentProperties . push_back ( PROPERTY_ID_DEFAULT_SELECT_SEQ ) ;
break ;
// ----- ListSource -----
case PROPERTY_ID_LISTSOURCE :
aDependentProperties . push_back ( PROPERTY_ID_STRINGITEMLIST ) ;
break ;
// ----- DataField -----
case PROPERTY_ID_CONTROLSOURCE :
{
: : rtl : : OUString sControlSource ;
_rNewValue > > = sControlSource ;
if ( impl_componentHasProperty_throw ( PROPERTY_FILTERPROPOSAL ) )
_rxInspectorUI - > enablePropertyUI ( PROPERTY_FILTERPROPOSAL , sControlSource . getLength ( ) > 0 ) ;
if ( impl_componentHasProperty_throw ( PROPERTY_EMPTY_IS_NULL ) )
_rxInspectorUI - > enablePropertyUI ( PROPERTY_EMPTY_IS_NULL , sControlSource . getLength ( ) > 0 ) ;
aDependentProperties . push_back ( PROPERTY_ID_BOUNDCOLUMN ) ;
aDependentProperties . push_back ( PROPERTY_ID_SCALEIMAGE ) ;
2008-12-01 12:31:27 +00:00
aDependentProperties . push_back ( PROPERTY_ID_SCALE_MODE ) ;
aDependentProperties . push_back ( PROPERTY_ID_INPUT_REQUIRED ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
break ;
2008-12-01 12:31:27 +00:00
case PROPERTY_ID_EMPTY_IS_NULL :
aDependentProperties . push_back ( PROPERTY_ID_INPUT_REQUIRED ) ;
break ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
// ----- SubmitEncoding -----
case PROPERTY_ID_SUBMIT_ENCODING :
{
FormSubmitEncoding eEncoding = FormSubmitEncoding_URL ;
OSL_VERIFY ( _rNewValue > > = eEncoding ) ;
_rxInspectorUI - > enablePropertyUI ( PROPERTY_SUBMIT_METHOD , eEncoding = = FormSubmitEncoding_URL ) ;
}
break ;
// ----- Repeat -----
case PROPERTY_ID_REPEAT :
{
sal_Bool bIsRepeating = sal_False ;
OSL_VERIFY ( _rNewValue > > = bIsRepeating ) ;
_rxInspectorUI - > enablePropertyUI ( PROPERTY_REPEAT_DELAY , bIsRepeating ) ;
}
break ;
// ----- TabStop -----
case PROPERTY_ID_TABSTOP :
{
if ( ! impl_componentHasProperty_throw ( PROPERTY_TABINDEX ) )
break ;
sal_Bool bHasTabStop = sal_False ;
_rNewValue > > = bHasTabStop ;
_rxInspectorUI - > enablePropertyUI ( PROPERTY_TABINDEX , bHasTabStop ) ;
}
break ;
// ----- Border -----
case PROPERTY_ID_BORDER :
{
sal_Int16 nBordeType = VisualEffect : : NONE ;
OSL_VERIFY ( _rNewValue > > = nBordeType ) ;
_rxInspectorUI - > enablePropertyUI ( PROPERTY_BORDERCOLOR , nBordeType = = VisualEffect : : FLAT ) ;
}
break ;
// ----- DropDown -----
case PROPERTY_ID_DROPDOWN :
{
if ( impl_isSupportedProperty_nothrow ( PROPERTY_ID_LINECOUNT ) )
{
sal_Bool bDropDown = sal_True ;
_rNewValue > > = bDropDown ;
_rxInspectorUI - > enablePropertyUI ( PROPERTY_LINECOUNT , bDropDown ) ;
}
}
break ;
// ----- ImageURL -----
case PROPERTY_ID_IMAGE_URL :
{
if ( impl_isSupportedProperty_nothrow ( PROPERTY_ID_IMAGEPOSITION ) )
{
: : rtl : : OUString sImageURL ;
OSL_VERIFY ( _rNewValue > > = sImageURL ) ;
_rxInspectorUI - > enablePropertyUI ( PROPERTY_IMAGEPOSITION , sImageURL . getLength ( ) ! = 0 ) ;
}
aDependentProperties . push_back ( PROPERTY_ID_SCALEIMAGE ) ;
2008-12-01 12:31:27 +00:00
aDependentProperties . push_back ( PROPERTY_ID_SCALE_MODE ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
break ;
// ----- ButtonType -----
case PROPERTY_ID_BUTTONTYPE :
{
FormButtonType eButtonType ( FormButtonType_PUSH ) ;
OSL_VERIFY ( _rNewValue > > = eButtonType ) ;
_rxInspectorUI - > enablePropertyUI ( PROPERTY_TARGET_URL , FormButtonType_URL = = eButtonType ) ;
}
// NO break!
// ----- TargetURL -----
case PROPERTY_ID_TARGET_URL :
aDependentProperties . push_back ( PROPERTY_ID_TARGET_FRAME ) ;
break ; // case PROPERTY_ID_TARGET_URL
// ----- TriState -----
case PROPERTY_ID_TRISTATE :
if ( ! _bFirstTimeInit )
CWS-TOOLING: integrate CWS dba32b
2009-06-03 14:58:08 +0200 fs r272581 : #i102439#
2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls
2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font
2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary
2009-05-27 15:30:22 +0200 msc r272353 : #102303#
2009-05-26 13:03:06 +0200 fs r272295 : spelling
2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes
2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only
2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them
2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2
2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett
2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member
2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model
2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate
2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate
2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name
2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets
2009-05-20 11:29:55 +0200 msc r272111 : #i100000#
2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a
2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work
2009-05-20 09:43:36 +0200 oj r272106 : clean up includes
2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt
2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010#
2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey
2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset
2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column
2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names
2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date
2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date
2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019#
2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019#
2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010#
2009-05-15 10:21:24 +0200 msc r271929 : #101944#
2009-05-11 21:18:30 +0200 fs r271792 : #i99914#
2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span
2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode
2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue)
2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx
2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet
2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape
2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler
2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting
2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name
2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type
2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar
2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table
2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well
2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text
2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary
2009-05-07 11:47:18 +0200 fs r271647 : #i10000#
2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI
2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw
2009-05-07 10:09:55 +0200 fs r271634 : #i101623#
2009-05-07 09:53:44 +0200 fs r271631 : #i101622#
2009-05-06 21:55:53 +0200 fs r271615 : #i10000#
2009-05-06 21:10:42 +0200 fs r271611 : #i10000#
2009-05-06 13:11:48 +0200 fs r271583 : #i10000#
2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message
2009-05-05 22:29:03 +0200 fs r271558 : diagnostics
2009-05-05 22:16:16 +0200 fs r271557 : #i10000#
2009-05-05 13:50:32 +0200 fs r271513 : #i10000#
2009-05-05 10:21:50 +0200 fs r271503 : #i10000#
2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step?
2009-05-05 09:18:12 +0200 fs r271500 : #i10000#
2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47)
2009-05-04 14:51:26 +0200 fs r271456 : line ends
2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL
2009-04-22 21:18:34 +0200 fs r271141 : #i100944#
2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change
2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes
2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes
2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes
2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before
2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed
2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows
2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart
2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter
2009-04-17 21:00:23 +0200 fs r270954 : #i98350#
2009-04-17 13:54:19 +0200 fs r270942 : #i99565#
2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model
2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include
2009-04-17 10:10:15 +0200 fs r270926 : #i10000#
2009-04-17 10:02:36 +0200 fs r270925 : #i10000#
2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx
2009-04-16 21:05:25 +0200 fs r270903 : #i10000#
2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual
2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property
2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too
2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-15 14:53:13 +0200 fs r270844 : #i10000#
2009-04-15 13:08:29 +0200 fs r270836 : #i10000#
2009-04-15 12:28:14 +0200 fs r270832 : #i10000#
2009-04-15 10:59:14 +0200 fs r270827 : #i10000#
2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd
2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified
2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj
2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType
2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property
2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx
2009-04-14 15:46:54 +0200 fs r270784 : diagnostics
2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context
2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const
2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces
2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2
2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest
2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height
2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well
2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns
2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report
2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report
2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report
2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report
2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends
2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report
2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report
2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report
2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report
2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report
2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report
2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein
2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary
2009-04-03 14:35:49 +0200 fs r270487 : #i10000#
2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too
2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties
2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it
2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position
2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name
2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein
2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics
2009-04-02 16:35:19 +0200 fs r270421 : diagnostics
2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead
2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters
2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein
2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein
2009-04-02 14:10:35 +0200 fs r270405 : #i10000#
2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein
2009-04-02 14:03:03 +0200 fs r270401 : #i10000#
2009-04-02 13:58:13 +0200 fs r270400 : #i10000#
2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein
2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes
2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein
2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein
2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header
2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein
2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein
2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein
2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types
2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein
2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein
2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein
2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/>
2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used
2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode
2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein
2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge
2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein
2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein
2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table
2009-03-30 09:36:24 +0200 fs r270195 : assertion text
2009-03-28 20:21:58 +0100 fs r270187 : #ii10000#
2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids
2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids
2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset
2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45)
2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes
2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring
2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths
2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values
2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN
2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN
2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter
2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys
2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox
2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition
2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button
2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition
2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition
2009-03-25 10:29:07 +0100 fs r270003 : add missing localization
2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed
2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb
2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation
2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb
2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control
2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK
2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style
2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust
2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type
2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb
2009-03-20 08:52:47 +0100 fs r269780 : doc
2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different
2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider
2009-03-19 22:52:52 +0100 fs r269771 : added comment
2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration
2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now.
2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object
2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups
2009-03-19 09:25:27 +0100 fs r269727 : #i10000#
2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance
2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks
2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation
2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency
2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports
2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet)
2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work
2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation
2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext
2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long
2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null
2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params
2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment
2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed
2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment
2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle
2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups
2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList
2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface
2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList
2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups
2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups
2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion
2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode
2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode
2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes
2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long
2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents
2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive
2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header
2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type
2009-03-16 14:14:16 +0100 fs r269537 : line ends
2009-03-16 14:11:06 +0100 fs r269535 : line ends
2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter
2009-03-16 12:30:31 +0100 oj r269521 : compile error
2009-03-16 12:19:12 +0100 oj r269519 : compile error
2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap
2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43)
2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :)
2009-03-12 14:35:07 +0100 fs r269414 : not needed
2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module
2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib
2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure)
2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move
2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk
2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore
2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:45:07 +0100 fs r269401 : moved from ../
2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider
2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error
2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests
2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat
2009-03-12 12:34:53 +0100 fs r269388 : new API tests
2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed
2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring
2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop
2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider
2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop
2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications
2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications
2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications
2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components
2009-03-12 10:30:37 +0100 fs r269367 : module-local includes
2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata
2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name
2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty
2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language
2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer
2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map
2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer
2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied
2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed
2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults
2009-03-06 17:20:30 +0100 fs r269029 : #i98600#
2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ...
2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed
2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option
2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now
2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms
2009-03-06 09:53:41 +0100 fs r268977 : #i10000#
2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems
2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted)
2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20
2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages
2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42
2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings
2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups
2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b
2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b
2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData
2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations
2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL
2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types
2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator !=
2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size
2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now
2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric
2009-02-19 15:43:12 +0100 fs r268291 : #i99415#
2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account
2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title
2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
_rxInspectorUI - > rebuildPropertyUI ( m_eComponentClass = = eFormControl ? PROPERTY_DEFAULT_STATE : PROPERTY_STATE ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
break ; // case PROPERTY_ID_TRISTATE
// ----- DecimalAccuracy -----
case PROPERTY_ID_DECIMAL_ACCURACY :
// ----- ShowThousandsSeparator -----
case PROPERTY_ID_SHOWTHOUSANDSEP :
{
sal_Bool bAccuracy = ( PROPERTY_ID_DECIMAL_ACCURACY = = nActuatingPropId ) ;
sal_uInt16 nNewDigits = 0 ;
sal_Bool bUseSep = sal_False ;
if ( bAccuracy )
OSL_VERIFY ( _rNewValue > > = nNewDigits ) ;
else
OSL_VERIFY ( _rNewValue > > = bUseSep ) ;
// propagate the changes to the min/max/default fields
Any aCurrentProp ;
: : rtl : : OUString aAffectedProps [ ] = { PROPERTY_VALUE , PROPERTY_DEFAULT_VALUE , PROPERTY_VALUEMIN , PROPERTY_VALUEMAX } ;
for ( sal_uInt16 i = 0 ; i < sizeof ( aAffectedProps ) / sizeof ( aAffectedProps [ 0 ] ) ; + + i )
{
Reference < XPropertyControl > xControl ;
try
{
xControl = _rxInspectorUI - > getPropertyControl ( aAffectedProps [ i ] ) ;
}
2006-07-26 06:56:33 +00:00
catch ( const UnknownPropertyException & e ) { ( void ) e ; }
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( xControl . is ( ) )
{
OFormattedNumericControl * pControl = dynamic_cast < OFormattedNumericControl * > ( xControl . get ( ) ) ;
DBG_ASSERT ( pControl , " FormComponentPropertyHandler::actuatingPropertyChanged: invalid control! " ) ;
if ( pControl )
2008-12-11 07:05:03 +00:00
{
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( bAccuracy )
pControl - > SetDecimalDigits ( nNewDigits ) ;
else
pControl - > SetThousandsSep ( bUseSep ) ;
2008-12-11 07:05:03 +00:00
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
}
}
break ;
// ----- FormatKey -----
case PROPERTY_ID_FORMATKEY :
{
FormatDescription aNewDesc ;
Reference < XNumberFormatsSupplier > xSupplier ;
OSL_VERIFY ( m_xComponent - > getPropertyValue ( PROPERTY_FORMATSSUPPLIER ) > > = xSupplier ) ;
Reference < XUnoTunnel > xTunnel ( xSupplier , UNO_QUERY ) ;
DBG_ASSERT ( xTunnel . is ( ) , " FormComponentPropertyHandler::actuatingPropertyChanged: xTunnel is invalid! " ) ;
2007-07-06 07:48:27 +00:00
if ( xTunnel . is ( ) )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
2007-07-06 07:48:27 +00:00
SvNumberFormatsSupplierObj * pSupplier = reinterpret_cast < SvNumberFormatsSupplierObj * > ( xTunnel - > getSomething ( SvNumberFormatsSupplierObj : : getUnoTunnelId ( ) ) ) ;
// the same again
aNewDesc . pSupplier = pSupplier ;
if ( ! ( _rNewValue > > = aNewDesc . nKey ) )
aNewDesc . nKey = 0 ;
// give each control which has to know this an own copy of the description
: : rtl : : OUString aFormattedPropertyControls [ ] = {
PROPERTY_EFFECTIVE_MIN , PROPERTY_EFFECTIVE_MAX , PROPERTY_EFFECTIVE_DEFAULT , PROPERTY_EFFECTIVE_VALUE
} ;
for ( sal_uInt16 i = 0 ; i < sizeof ( aFormattedPropertyControls ) / sizeof ( aFormattedPropertyControls [ 0 ] ) ; + + i )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
2007-07-06 07:48:27 +00:00
Reference < XPropertyControl > xControl ;
try
{
xControl = _rxInspectorUI - > getPropertyControl ( aFormattedPropertyControls [ i ] ) ;
}
catch ( const UnknownPropertyException & e ) { ( void ) e ; }
if ( xControl . is ( ) )
{
OFormattedNumericControl * pControl = dynamic_cast < OFormattedNumericControl * > ( xControl . get ( ) ) ;
DBG_ASSERT ( pControl , " FormComponentPropertyHandler::actuatingPropertyChanged: invalid control! " ) ;
if ( pControl )
pControl - > SetFormatDescription ( aNewDesc ) ;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
}
}
break ;
CWS-TOOLING: integrate CWS dba32b
2009-06-03 14:58:08 +0200 fs r272581 : #i102439#
2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls
2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font
2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary
2009-05-27 15:30:22 +0200 msc r272353 : #102303#
2009-05-26 13:03:06 +0200 fs r272295 : spelling
2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes
2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only
2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them
2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2
2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett
2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member
2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model
2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate
2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate
2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name
2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets
2009-05-20 11:29:55 +0200 msc r272111 : #i100000#
2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a
2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work
2009-05-20 09:43:36 +0200 oj r272106 : clean up includes
2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt
2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010#
2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey
2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset
2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column
2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names
2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date
2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date
2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019#
2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019#
2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010#
2009-05-15 10:21:24 +0200 msc r271929 : #101944#
2009-05-11 21:18:30 +0200 fs r271792 : #i99914#
2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span
2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode
2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue)
2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx
2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet
2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape
2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath
2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler
2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting
2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name
2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type
2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar
2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table
2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well
2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text
2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary
2009-05-07 11:47:18 +0200 fs r271647 : #i10000#
2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI
2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw
2009-05-07 10:09:55 +0200 fs r271634 : #i101623#
2009-05-07 09:53:44 +0200 fs r271631 : #i101622#
2009-05-06 21:55:53 +0200 fs r271615 : #i10000#
2009-05-06 21:10:42 +0200 fs r271611 : #i10000#
2009-05-06 13:11:48 +0200 fs r271583 : #i10000#
2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message
2009-05-05 22:29:03 +0200 fs r271558 : diagnostics
2009-05-05 22:16:16 +0200 fs r271557 : #i10000#
2009-05-05 13:50:32 +0200 fs r271513 : #i10000#
2009-05-05 10:21:50 +0200 fs r271503 : #i10000#
2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step?
2009-05-05 09:18:12 +0200 fs r271500 : #i10000#
2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47)
2009-05-04 14:51:26 +0200 fs r271456 : line ends
2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL
2009-04-22 21:18:34 +0200 fs r271141 : #i100944#
2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change
2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes
2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes
2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes
2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before
2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before
2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed
2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows
2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart
2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter
2009-04-17 21:00:23 +0200 fs r270954 : #i98350#
2009-04-17 13:54:19 +0200 fs r270942 : #i99565#
2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model
2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include
2009-04-17 10:10:15 +0200 fs r270926 : #i10000#
2009-04-17 10:02:36 +0200 fs r270925 : #i10000#
2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes
2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx
2009-04-16 21:05:25 +0200 fs r270903 : #i10000#
2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual
2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property
2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too
2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too
2009-04-15 14:53:13 +0200 fs r270844 : #i10000#
2009-04-15 13:08:29 +0200 fs r270836 : #i10000#
2009-04-15 12:28:14 +0200 fs r270832 : #i10000#
2009-04-15 10:59:14 +0200 fs r270827 : #i10000#
2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd
2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified
2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj
2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType
2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property
2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx
2009-04-14 15:46:54 +0200 fs r270784 : diagnostics
2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class
2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context
2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const
2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces
2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2
2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest
2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height
2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well
2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns
2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report
2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report
2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report
2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report
2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends
2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report
2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report
2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report
2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report
2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report
2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report
2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein
2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary
2009-04-03 14:35:49 +0200 fs r270487 : #i10000#
2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too
2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties
2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it
2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position
2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name
2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein
2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics
2009-04-02 16:35:19 +0200 fs r270421 : diagnostics
2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead
2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters
2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein
2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein
2009-04-02 14:10:35 +0200 fs r270405 : #i10000#
2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein
2009-04-02 14:03:03 +0200 fs r270401 : #i10000#
2009-04-02 13:58:13 +0200 fs r270400 : #i10000#
2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein
2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes
2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein
2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein
2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header
2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein
2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein
2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein
2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types
2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein
2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein
2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein
2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/>
2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used
2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode
2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein
2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge
2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein
2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein
2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table
2009-03-30 09:36:24 +0200 fs r270195 : assertion text
2009-03-28 20:21:58 +0100 fs r270187 : #ii10000#
2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids
2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids
2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset
2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45)
2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes
2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE
2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring
2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths
2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values
2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN
2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN
2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter
2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys
2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it
2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox
2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition
2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button
2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition
2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition
2009-03-25 10:29:07 +0100 fs r270003 : add missing localization
2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#:
rework the error handling, allow using css.sdb.ErrorCondition values, plus
allow propagating the nsresult
2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed
2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb
2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation
2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb
2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control
2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK
2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style
2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust
2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type
2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb
2009-03-20 08:52:47 +0100 fs r269780 : doc
2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different
2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider
2009-03-19 22:52:52 +0100 fs r269771 : added comment
2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration
2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now.
2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object
2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups
2009-03-19 09:25:27 +0100 fs r269727 : #i10000#
2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance
2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks
2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation
2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency
2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports
2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet)
2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work
2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation
2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext
2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long
2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null
2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params
2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment
2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed
2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment
2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle
2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups
2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList
2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface
2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList
2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups
2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups
2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion
2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode
2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode
2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes
2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long
2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents
2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive
2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header
2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type
2009-03-16 14:14:16 +0100 fs r269537 : line ends
2009-03-16 14:11:06 +0100 fs r269535 : line ends
2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter
2009-03-16 12:30:31 +0100 oj r269521 : compile error
2009-03-16 12:19:12 +0100 oj r269519 : compile error
2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap
2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43)
2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :)
2009-03-12 14:35:07 +0100 fs r269414 : not needed
2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module
2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib
2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure)
2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move
2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk
2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore
2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:45:07 +0100 fs r269401 : moved from ../
2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure
2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider
2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error
2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests
2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat
2009-03-12 12:34:53 +0100 fs r269388 : new API tests
2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed
2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring
2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop
2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider
2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop
2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications
2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications
2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications
2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components
2009-03-12 10:30:37 +0100 fs r269367 : module-local includes
2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata
2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name
2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty
2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language
2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer
2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map
2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer
2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied
2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed
2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults
2009-03-06 17:20:30 +0100 fs r269029 : #i98600#
2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ...
2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed
2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option
2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now
2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms
2009-03-06 09:53:41 +0100 fs r268977 : #i10000#
2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems
2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted)
2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20
2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages
2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42
2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings
2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42)
2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups
2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b
2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b
2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData
2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations
2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL
2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types
2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator !=
2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size
2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now
2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric
2009-02-19 15:43:12 +0100 fs r268291 : #i99415#
2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account
2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title
2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
case PROPERTY_ID_TOGGLE :
{
sal_Bool bIsToggleButton = sal_False ;
OSL_VERIFY ( _rNewValue > > = bIsToggleButton ) ;
_rxInspectorUI - > enablePropertyUI ( PROPERTY_DEFAULT_STATE , bIsToggleButton ) ;
}
break ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
default :
DBG_ERROR ( " FormComponentPropertyHandler::actuatingPropertyChanged: did not register for this property! " ) ;
break ;
} // switch ( nActuatingPropId )
for ( : : std : : vector < PropertyId > : : const_iterator loopAffected = aDependentProperties . begin ( ) ;
loopAffected ! = aDependentProperties . end ( ) ;
+ + loopAffected
)
{
if ( impl_isSupportedProperty_nothrow ( * loopAffected ) )
impl_updateDependentProperty_nothrow ( * loopAffected , _rxInspectorUI ) ;
}
}
//------------------------------------------------------------------------
void FormComponentPropertyHandler : : impl_updateDependentProperty_nothrow ( PropertyId _nPropId , const Reference < XObjectInspectorUI > & _rxInspectorUI ) const
{
try
{
switch ( _nPropId )
{
// ----- StringItemList -----
case PROPERTY_ID_STRINGITEMLIST :
{
ListSourceType eLSType = ListSourceType_VALUELIST ;
OSL_VERIFY ( impl_getPropertyValue_throw ( PROPERTY_LISTSOURCETYPE ) > > = eLSType ) ;
: : rtl : : OUString sListSource ;
{
Sequence < : : rtl : : OUString > aListSource ;
Any aListSourceValue ( impl_getPropertyValue_throw ( PROPERTY_LISTSOURCE ) ) ;
if ( aListSourceValue > > = aListSource )
{
if ( aListSource . getLength ( ) )
sListSource = aListSource [ 0 ] ;
}
else
OSL_VERIFY ( aListSourceValue > > = sListSource ) ;
}
sal_Bool bIsEnabled = ( ( eLSType = = ListSourceType_VALUELIST )
| | ( sListSource . getLength ( ) = = 0 )
) ;
_rxInspectorUI - > enablePropertyUI ( PROPERTY_STRINGITEMLIST , bIsEnabled ) ;
}
break ; // case PROPERTY_ID_STRINGITEMLIST
// ----- BoundColumn -----
case PROPERTY_ID_BOUNDCOLUMN :
{
: : rtl : : OUString sControlSource ;
OSL_VERIFY ( impl_getPropertyValue_throw ( PROPERTY_CONTROLSOURCE ) > > = sControlSource ) ;
ListSourceType eLSType = ListSourceType_VALUELIST ;
OSL_VERIFY ( impl_getPropertyValue_throw ( PROPERTY_LISTSOURCETYPE ) > > = eLSType ) ;
_rxInspectorUI - > enablePropertyUI ( PROPERTY_BOUNDCOLUMN ,
( sControlSource . getLength ( ) > 0 )
& & ( eLSType ! = ListSourceType_TABLEFIELDS )
& & ( eLSType ! = ListSourceType_VALUELIST )
) ;
}
break ; // case PROPERTY_ID_BOUNDCOLUMN
2008-12-01 12:31:27 +00:00
// ----- ScaleImage, ScaleMode -----
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_SCALEIMAGE :
2008-12-01 12:31:27 +00:00
case PROPERTY_ID_SCALE_MODE :
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
: : rtl : : OUString sControlSource ;
if ( impl_isSupportedProperty_nothrow ( PROPERTY_ID_CONTROLSOURCE ) )
impl_getPropertyValue_throw ( PROPERTY_CONTROLSOURCE ) > > = sControlSource ;
: : rtl : : OUString sImageURL ;
impl_getPropertyValue_throw ( PROPERTY_IMAGE_URL ) > > = sImageURL ;
2008-12-01 12:31:27 +00:00
_rxInspectorUI - > enablePropertyUI ( impl_getPropertyNameFromId_nothrow ( _nPropId ) ,
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
( sControlSource . getLength ( ) ! = 0 ) | | ( sImageURL . getLength ( ) ! = 0 )
) ;
}
2008-12-01 12:31:27 +00:00
break ; // case PROPERTY_ID_SCALEIMAGE, PROPERTY_ID_SCALE_MODE
// ----- InputRequired -----
case PROPERTY_ID_INPUT_REQUIRED :
{
: : rtl : : OUString sControlSource ;
OSL_VERIFY ( impl_getPropertyValue_throw ( PROPERTY_CONTROLSOURCE ) > > = sControlSource ) ;
sal_Bool bEmptyIsNULL = sal_False ;
sal_Bool bHasEmptyIsNULL = impl_componentHasProperty_throw ( PROPERTY_EMPTY_IS_NULL ) ;
if ( bHasEmptyIsNULL )
OSL_VERIFY ( impl_getPropertyValue_throw ( PROPERTY_EMPTY_IS_NULL ) > > = bEmptyIsNULL ) ;
// if the control is not bound to a DB field, there is no sense in having the "Input required"
// property
// Also, if an empty input of this control are *not* written as NULL, but as empty strings,
// then "Input required" does not make sense, too (since there's always an input, even if the control
// is empty).
_rxInspectorUI - > enablePropertyUI ( PROPERTY_INPUT_REQUIRED ,
( sControlSource . getLength ( ) ! = 0 ) & & ( ! bHasEmptyIsNULL | | bEmptyIsNULL )
) ;
}
break ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
2008-12-01 12:31:27 +00:00
// ----- SelectedItems, DefaultSelection -----
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_SELECTEDITEMS :
case PROPERTY_ID_DEFAULT_SELECT_SEQ :
{
Sequence < : : rtl : : OUString > aEntries ;
impl_getPropertyValue_throw ( PROPERTY_STRINGITEMLIST ) > > = aEntries ;
bool isEnabled = aEntries . getLength ( ) ! = 0 ;
if ( ( m_nClassId = = FormComponentType : : LISTBOX ) & & ( m_eComponentClass = = eFormControl ) )
{
ListSourceType eLSType = ListSourceType_VALUELIST ;
impl_getPropertyValue_throw ( PROPERTY_LISTSOURCETYPE ) > > = eLSType ;
isEnabled & = ( eLSType = = ListSourceType_VALUELIST ) ;
}
_rxInspectorUI - > enablePropertyUIElements ( impl_getPropertyNameFromId_nothrow ( _nPropId ) ,
PropertyLineElement : : PrimaryButton , isEnabled ) ;
}
break ; // case PROPERTY_ID_DEFAULT_SELECT_SEQ
// ----- TargetFrame ------
case PROPERTY_ID_TARGET_FRAME :
{
: : rtl : : OUString sTargetURL ;
impl_getPropertyValue_throw ( PROPERTY_TARGET_URL ) > > = sTargetURL ;
FormButtonType eButtonType ( FormButtonType_URL ) ;
if ( 0 ! = m_nClassId )
{
OSL_VERIFY ( impl_getPropertyValue_throw ( PROPERTY_BUTTONTYPE ) > > = eButtonType ) ;
}
// if m_nClassId is 0, then we're inspecting a form. In this case, eButtonType is always
// FormButtonType_URL here
_rxInspectorUI - > enablePropertyUI ( PROPERTY_TARGET_FRAME ,
( eButtonType = = FormButtonType_URL ) & & ( sTargetURL . getLength ( ) > 0 )
) ;
}
break ;
// ----- Order ------
case PROPERTY_ID_SORT :
// ----- Filter ------
case PROPERTY_ID_FILTER :
{
Reference < XConnection > xConnection ;
bool bAllowEmptyDS = : : dbtools : : isEmbeddedInDatabase ( m_xComponent , xConnection ) ;
// if there's no escape processing, we cannot enter any values for this property
sal_Bool bDoEscapeProcessing ( sal_False ) ;
impl_getPropertyValue_throw ( PROPERTY_ESCAPE_PROCESSING ) > > = bDoEscapeProcessing ;
_rxInspectorUI - > enablePropertyUI (
impl_getPropertyNameFromId_nothrow ( _nPropId ) ,
bDoEscapeProcessing
) ;
// also care for the browse button - enabled if we have escape processing, and a valid
// data source signature
_rxInspectorUI - > enablePropertyUIElements (
impl_getPropertyNameFromId_nothrow ( _nPropId ) ,
PropertyLineElement : : PrimaryButton ,
2007-07-06 07:48:27 +00:00
impl_hasValidDataSourceSignature_nothrow ( m_xComponent , bAllowEmptyDS )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
& & bDoEscapeProcessing
) ;
}
break ; // case PROPERTY_ID_FILTER:
// ----- Command -----
case PROPERTY_ID_COMMAND :
{
2007-11-21 15:21:57 +00:00
sal_Int32 nCommandType ( CommandType : : COMMAND ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
OSL_VERIFY ( impl_getPropertyValue_throw ( PROPERTY_COMMANDTYPE ) > > = nCommandType ) ;
2007-07-06 07:48:27 +00:00
impl_ensureRowsetConnection_nothrow ( ) ;
2007-11-21 15:21:57 +00:00
Reference < XConnection > xConnection = m_xRowSetConnection . getTyped ( ) ;
2007-07-06 07:48:27 +00:00
bool bAllowEmptyDS = false ;
if ( ! xConnection . is ( ) )
bAllowEmptyDS = : : dbtools : : isEmbeddedInDatabase ( m_xComponent , xConnection ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
bool doEnable = ( nCommandType = = CommandType : : COMMAND )
& & ( m_xRowSetConnection . is ( )
2007-07-06 07:48:27 +00:00
| | xConnection . is ( )
| | impl_hasValidDataSourceSignature_nothrow ( m_xComponent , bAllowEmptyDS )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
) ;
_rxInspectorUI - > enablePropertyUIElements (
PROPERTY_COMMAND ,
PropertyLineElement : : PrimaryButton ,
doEnable
) ;
}
break ; // case PROPERTY_ID_COMMAND
// ----- DetailFields -----
case PROPERTY_ID_DETAILFIELDS :
{
Reference < XConnection > xConnection ;
bool bAllowEmptyDS = : : dbtools : : isEmbeddedInDatabase ( m_xComponent , xConnection ) ;
// both our current form, and it's parent form, need to have a valid
// data source signature
2007-07-06 07:48:27 +00:00
bool bDoEnableMasterDetailFields =
impl_hasValidDataSourceSignature_nothrow ( m_xComponent , bAllowEmptyDS )
& & impl_hasValidDataSourceSignature_nothrow ( Reference < XPropertySet > ( m_xObjectParent , UNO_QUERY ) , bAllowEmptyDS ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
// in opposite to the other properties, here in real *two* properties are
// affected
2007-07-06 07:48:27 +00:00
_rxInspectorUI - > enablePropertyUIElements ( PROPERTY_DETAILFIELDS , PropertyLineElement : : PrimaryButton , bDoEnableMasterDetailFields ) ;
_rxInspectorUI - > enablePropertyUIElements ( PROPERTY_MASTERFIELDS , PropertyLineElement : : PrimaryButton , bDoEnableMasterDetailFields ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
break ;
default :
OSL_ENSURE ( false , " FormComponentPropertyHandler::impl_updateDependentProperty_nothrow: unexpected property to update! " ) ;
break ;
} // switch
}
catch ( const Exception & )
{
OSL_ENSURE ( sal_False , " FormComponentPropertyHandler::impl_updateDependentProperty_nothrow: caught an exception! " ) ;
}
}
//------------------------------------------------------------------------
void SAL_CALL FormComponentPropertyHandler : : disposing ( )
{
FormComponentPropertyHandler_Base : : disposing ( ) ;
if ( m_xCommandDesigner . is ( ) & & m_xCommandDesigner - > isActive ( ) )
m_xCommandDesigner - > dispose ( ) ;
}
//------------------------------------------------------------------------
sal_Bool SAL_CALL FormComponentPropertyHandler : : suspend ( sal_Bool _bSuspend ) throw ( RuntimeException )
{
: : osl : : MutexGuard aGuard ( m_aMutex ) ;
if ( _bSuspend )
if ( m_xCommandDesigner . is ( ) & & m_xCommandDesigner - > isActive ( ) )
return m_xCommandDesigner - > suspend ( ) ;
return sal_True ;
}
//------------------------------------------------------------------------
void FormComponentPropertyHandler : : impl_initComponentMetaData_throw ( )
{
try
{
//////////////////////////////////////////////////////////////////
// component class
m_eComponentClass = eUnknown ;
if ( impl_componentHasProperty_throw ( PROPERTY_WIDTH )
& & impl_componentHasProperty_throw ( PROPERTY_HEIGHT )
& & impl_componentHasProperty_throw ( PROPERTY_POSITIONX )
& & impl_componentHasProperty_throw ( PROPERTY_POSITIONY )
2007-07-06 07:48:27 +00:00
& & impl_componentHasProperty_throw ( PROPERTY_STEP )
& & impl_componentHasProperty_throw ( PROPERTY_TABINDEX )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
)
{
m_eComponentClass = eDialogControl ;
}
else
{
m_eComponentClass = eFormControl ;
}
//////////////////////////////////////////////////////////////////
// (database) sub form?
Reference < XForm > xAsForm ( m_xComponent , UNO_QUERY ) ;
if ( xAsForm . is ( ) )
{
Reference < XChild > xFormAsChild ( xAsForm , UNO_QUERY ) ;
Reference < XForm > xFormsParent ;
if ( xFormAsChild . is ( ) )
xFormsParent = xFormsParent . query ( xFormAsChild - > getParent ( ) ) ;
m_bComponentIsSubForm = xFormsParent . is ( ) ;
}
//////////////////////////////////////////////////////////////////
// ClassId
Reference < XChild > xCompAsChild ( m_xComponent , UNO_QUERY ) ;
if ( xCompAsChild . is ( ) )
m_xObjectParent = xCompAsChild - > getParent ( ) ;
//////////////////////////////////////////////////////////////////
// ClassId
impl_classifyControlModel_throw ( ) ;
}
catch ( const RuntimeException & )
{
throw ;
}
catch ( const Exception & )
{
OSL_ENSURE ( sal_False , " FormComponentPropertyHandler::impl_initComponentMetaData_throw: caught an exception! " ) ;
}
}
//------------------------------------------------------------------------
void FormComponentPropertyHandler : : impl_classifyControlModel_throw ( )
{
if ( impl_componentHasProperty_throw ( PROPERTY_CLASSID ) )
{
OSL_VERIFY ( m_xComponent - > getPropertyValue ( PROPERTY_CLASSID ) > > = m_nClassId ) ;
}
else if ( eDialogControl = = m_eComponentClass )
{
Reference < XControlModel > xControlModel ( m_xComponent , UNO_QUERY ) ;
2007-07-06 07:48:27 +00:00
Reference < XServiceInfo > xServiceInfo ( m_xComponent , UNO_QUERY ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( xServiceInfo . is ( ) )
{
// it's a control model, and can tell about it's supported services
m_nClassId = FormComponentType : : CONTROL ;
const sal_Char * aControlModelServiceNames [ ] =
{
" UnoControlButtonModel " ,
" UnoControlCheckBoxModel " ,
" UnoControlComboBoxModel " ,
" UnoControlCurrencyFieldModel " ,
" UnoControlDateFieldModel " ,
" UnoControlEditModel " ,
" UnoControlFileControlModel " ,
" UnoControlFixedTextModel " ,
" UnoControlGroupBoxModel " ,
" UnoControlImageControlModel " ,
" UnoControlListBoxModel " ,
" UnoControlNumericFieldModel " ,
" UnoControlPatternFieldModel " ,
" UnoControlRadioButtonModel " ,
" UnoControlScrollBarModel " ,
" UnoControlSpinButtonModel " ,
" UnoControlTimeFieldModel " ,
" UnoControlFixedLineModel " ,
" UnoControlFormattedFieldModel " ,
" UnoControlProgressBarModel "
} ;
const sal_Int16 nClassIDs [ ] =
{
FormComponentType : : COMMANDBUTTON ,
FormComponentType : : CHECKBOX ,
FormComponentType : : COMBOBOX ,
FormComponentType : : CURRENCYFIELD ,
FormComponentType : : DATEFIELD ,
FormComponentType : : TEXTFIELD ,
FormComponentType : : FILECONTROL ,
FormComponentType : : FIXEDTEXT ,
FormComponentType : : GROUPBOX ,
FormComponentType : : IMAGECONTROL ,
FormComponentType : : LISTBOX ,
FormComponentType : : NUMERICFIELD ,
FormComponentType : : PATTERNFIELD ,
FormComponentType : : RADIOBUTTON ,
FormComponentType : : SCROLLBAR ,
FormComponentType : : SPINBUTTON ,
FormComponentType : : TIMEFIELD ,
ControlType : : FIXEDLINE ,
ControlType : : FORMATTEDFIELD ,
ControlType : : PROGRESSBAR
} ;
sal_Int32 nKnownControlTypes = sizeof ( aControlModelServiceNames ) / sizeof ( aControlModelServiceNames [ 0 ] ) ;
OSL_ENSURE ( nKnownControlTypes = = sizeof ( nClassIDs ) / sizeof ( nClassIDs [ 0 ] ) ,
" FormComponentPropertyHandler::impl_classifyControlModel_throw: inconsistence " ) ;
for ( sal_Int32 i = 0 ; i < nKnownControlTypes ; + + i )
{
: : rtl : : OUString sServiceName ( RTL_CONSTASCII_USTRINGPARAM ( " com.sun.star.awt. " ) ) ;
sServiceName + = : : rtl : : OUString : : createFromAscii ( aControlModelServiceNames [ i ] ) ;
if ( xServiceInfo - > supportsService ( sServiceName ) )
{
m_nClassId = nClassIDs [ i ] ;
break ;
}
}
}
}
}
//------------------------------------------------------------------------
void FormComponentPropertyHandler : : impl_normalizePropertyValue_nothrow ( Any & _rValue , PropertyId _nPropId ) const
{
switch ( _nPropId )
{
case PROPERTY_ID_TABSTOP :
if ( ! _rValue . hasValue ( ) )
{
switch ( m_nClassId )
{
case FormComponentType : : COMMANDBUTTON :
case FormComponentType : : RADIOBUTTON :
case FormComponentType : : CHECKBOX :
case FormComponentType : : TEXTFIELD :
case FormComponentType : : LISTBOX :
case FormComponentType : : COMBOBOX :
case FormComponentType : : FILECONTROL :
case FormComponentType : : DATEFIELD :
case FormComponentType : : TIMEFIELD :
case FormComponentType : : NUMERICFIELD :
case ControlType : : FORMATTEDFIELD :
case FormComponentType : : CURRENCYFIELD :
case FormComponentType : : PATTERNFIELD :
_rValue = makeAny ( ( sal_Bool ) sal_True ) ;
break ;
default :
_rValue = makeAny ( ( sal_Bool ) sal_False ) ;
break ;
}
}
break ;
}
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_shouldExcludeProperty_nothrow ( const Property & _rProperty ) const
{
OSL_ENSURE ( _rProperty . Handle = = m_pInfoService - > getPropertyId ( _rProperty . Name ) ,
" FormComponentPropertyHandler::impl_shouldExcludeProperty_nothrow: insonsistency in the property! " ) ;
if ( _rProperty . Handle = = PROPERTY_ID_CONTROLLABEL )
// prevent that this is caught below
return false ;
if ( ( _rProperty . Type . getTypeClass ( ) = = TypeClass_INTERFACE )
| | ( _rProperty . Type . getTypeClass ( ) = = TypeClass_ARRAY )
| | ( _rProperty . Type . getTypeClass ( ) = = TypeClass_UNKNOWN )
)
return true ;
if ( ( _rProperty . Attributes & PropertyAttribute : : TRANSIENT ) & & ( m_eComponentClass ! = eDialogControl ) )
// strange enough, dialog controls declare a lot of their properties as transient
return true ;
if ( _rProperty . Attributes & PropertyAttribute : : READONLY )
return true ;
switch ( _rProperty . Handle )
{
case PROPERTY_ID_MASTERFIELDS :
case PROPERTY_ID_DETAILFIELDS :
if ( ! m_bComponentIsSubForm )
// no master and detail fields for forms which are no sub forms
return true ;
break ;
case PROPERTY_ID_DATASOURCE :
{
// don't show DataSource if the component is part of an embedded form document
Reference < XConnection > xConn ;
if ( isEmbeddedInDatabase ( m_xComponent , xConn ) )
return true ;
}
break ;
case PROPERTY_ID_TEXT :
// don't show the "Text" property of formatted fields
if ( ControlType : : FORMATTEDFIELD = = m_nClassId )
return true ;
break ;
case PROPERTY_ID_FORMATKEY :
case PROPERTY_ID_EFFECTIVE_MIN :
case PROPERTY_ID_EFFECTIVE_MAX :
case PROPERTY_ID_EFFECTIVE_DEFAULT :
case PROPERTY_ID_EFFECTIVE_VALUE :
// only if the set has a formats supplier, too
if ( ! impl_componentHasProperty_throw ( PROPERTY_FORMATSSUPPLIER ) )
return true ;
// (form) date and time fields also have a formats supplier, but the format itself
// is reflected in another property
if ( ( FormComponentType : : DATEFIELD = = m_nClassId )
| | ( FormComponentType : : TIMEFIELD = = m_nClassId )
)
return true ;
break ;
2008-12-01 12:31:27 +00:00
case PROPERTY_ID_SCALEIMAGE :
if ( impl_componentHasProperty_throw ( PROPERTY_SCALE_MODE ) )
// ScaleImage is superseded by ScaleMode
return true ;
break ;
2008-12-16 13:30:53 +00:00
case PROPERTY_ID_WRITING_MODE :
if ( ! SvtCTLOptions ( ) . IsCTLFontEnabled ( ) )
return true ;
break ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
sal_uInt32 nPropertyUIFlags = m_pInfoService - > getPropertyUIFlags ( _rProperty . Handle ) ;
// don't show experimental properties unless allowed to do so
if ( ( nPropertyUIFlags & PROP_FLAG_EXPERIMENTAL ) ! = 0 )
{
if ( true ) // TODO
return true ;
}
// no data properties if no Base is installed. #124939#
// This fix is not intendend to appear on the main trunk. If you find it there,
// please tell me! frank.schoenheit@sun.com
if ( ( nPropertyUIFlags & PROP_FLAG_DATA_PROPERTY ) ! = 0 )
if ( ! SvtModuleOptions ( ) . IsModuleInstalled ( SvtModuleOptions : : E_SDATABASE ) )
return true ;
return false ;
}
//------------------------------------------------------------------------
Reference < XRowSet > FormComponentPropertyHandler : : impl_getRowSet_throw ( ) const
{
2007-07-06 07:48:27 +00:00
Reference < XRowSet > xRowSet = m_xRowSet ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( ! xRowSet . is ( ) )
{
2007-07-06 07:48:27 +00:00
xRowSet . set ( m_xComponent , UNO_QUERY ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( ! xRowSet . is ( ) )
{
2007-07-06 07:48:27 +00:00
xRowSet = Reference < XRowSet > ( m_xObjectParent , UNO_QUERY ) ;
if ( ! xRowSet . is ( ) )
{
// are we inspecting a grid column?
if ( Reference < XGridColumnFactory > ( m_xObjectParent , UNO_QUERY ) . is ( ) )
{ // yes
Reference < XChild > xParentAsChild ( m_xObjectParent , UNO_QUERY ) ;
if ( xParentAsChild . is ( ) )
xRowSet = Reference < XRowSet > ( xParentAsChild - > getParent ( ) , UNO_QUERY ) ;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
2007-07-06 07:48:27 +00:00
if ( ! xRowSet . is ( ) )
xRowSet = m_xRowSet ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
2007-07-06 07:48:27 +00:00
DBG_ASSERT ( xRowSet . is ( ) , " FormComponentPropertyHandler::impl_getRowSet_throw: could not obtain the rowset for the introspectee! " ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
return xRowSet ;
}
//------------------------------------------------------------------------
Reference < XRowSet > FormComponentPropertyHandler : : impl_getRowSet_nothrow ( ) const
{
Reference < XRowSet > xReturn ;
try
{
xReturn = impl_getRowSet_throw ( ) ;
}
catch ( const Exception & )
{
OSL_ENSURE ( sal_False , " FormComponentPropertyHandler::impl_getRowSet_nothrow: caught an exception! " ) ;
}
return xReturn ;
}
//------------------------------------------------------------------------
void FormComponentPropertyHandler : : impl_initFieldList_nothrow ( : : std : : vector < : : rtl : : OUString > & _rFieldNames ) const
{
clearContainer ( _rFieldNames ) ;
try
{
WaitCursor aWaitCursor ( impl_getDefaultDialogParent_nothrow ( ) ) ;
Reference < XPreparedStatement > xStatement ;
// get the form of the control we're inspecting
Reference < XPropertySet > xFormSet ( impl_getRowSet_throw ( ) , UNO_QUERY ) ;
if ( ! xFormSet . is ( ) )
return ;
: : rtl : : OUString sObjectName ;
OSL_VERIFY ( xFormSet - > getPropertyValue ( PROPERTY_COMMAND ) > > = sObjectName ) ;
// when there is no command we don't need to ask for columns
if ( sObjectName . getLength ( ) & & impl_ensureRowsetConnection_nothrow ( ) )
{
: : rtl : : OUString aDatabaseName ;
OSL_VERIFY ( xFormSet - > getPropertyValue ( PROPERTY_DATASOURCE ) > > = aDatabaseName ) ;
sal_Int32 nObjectType = CommandType : : COMMAND ;
OSL_VERIFY ( xFormSet - > getPropertyValue ( PROPERTY_COMMANDTYPE ) > > = nObjectType ) ;
Sequence < : : rtl : : OUString > aFields ( : : dbtools : : getFieldNamesByCommandDescriptor ( m_xRowSetConnection , nObjectType , sObjectName ) ) ;
const : : rtl : : OUString * pFields = aFields . getConstArray ( ) ;
for ( sal_Int32 i = 0 ; i < aFields . getLength ( ) ; + + i , + + pFields )
_rFieldNames . push_back ( * pFields ) ;
}
}
catch ( Exception & )
{
2008-11-10 15:06:12 +00:00
DBG_ERROR ( " FormComponentPropertyHandler::impl_initFieldList_nothrow: caught an exception! " ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
}
//------------------------------------------------------------------------
void FormComponentPropertyHandler : : impl_clearRowsetConnection_nothrow ( )
{
m_xRowSetConnection . clear ( ) ;
}
//------------------------------------------------------------------------
void FormComponentPropertyHandler : : impl_displaySQLError_nothrow ( const : : dbtools : : SQLExceptionInfo & _rErrorDescriptor ) const
{
: : dbtools : : showError ( _rErrorDescriptor , VCLUnoHelper : : GetInterface ( impl_getDefaultDialogParent_nothrow ( ) ) , m_aContext . getLegacyServiceFactory ( ) ) ;
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_ensureRowsetConnection_nothrow ( ) const
{
2007-07-06 07:48:27 +00:00
if ( ! m_xRowSetConnection . is ( ) )
{
uno : : Reference < sdbc : : XConnection > xConnection ( m_aContext . getContextValueByAsciiName ( " ActiveConnection " ) , uno : : UNO_QUERY ) ;
m_xRowSetConnection . reset ( xConnection , : : dbtools : : SharedConnection : : NoTakeOwnership ) ;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
if ( m_xRowSetConnection . is ( ) )
return true ;
Reference < XRowSet > xRowSet ( impl_getRowSet_throw ( ) ) ;
Reference < XPropertySet > xRowSetProps ( xRowSet , UNO_QUERY ) ;
// connect the row set - this is delegated to elsewhere - while observing errors
SQLExceptionInfo aError ;
try
{
if ( xRowSetProps . is ( ) )
{
WaitCursor aWaitCursor ( impl_getDefaultDialogParent_nothrow ( ) ) ;
m_xRowSetConnection = : : dbtools : : ensureRowSetConnection ( xRowSet , m_aContext . getLegacyServiceFactory ( ) , false ) ;
}
}
2007-05-10 09:47:38 +00:00
catch ( const SQLException & ) { aError = SQLExceptionInfo ( : : cppu : : getCaughtException ( ) ) ; }
catch ( const WrappedTargetException & e ) { aError = SQLExceptionInfo ( e . TargetException ) ; }
catch ( const Exception & ) { DBG_UNHANDLED_EXCEPTION ( ) ; }
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
// report errors, if necessary
if ( aError . isValid ( ) )
{
: : rtl : : OUString sDataSourceName ;
try
{
xRowSetProps - > getPropertyValue ( PROPERTY_DATASOURCE ) > > = sDataSourceName ;
}
catch ( const Exception & )
{
DBG_ERROR ( " FormComponentPropertyHandler::impl_ensureRowsetConnection_nothrow: caught an exception during error handling! " ) ;
}
// additional info about what happended
String sInfo ( PcrRes ( RID_STR_UNABLETOCONNECT ) ) ;
INetURLObject aParser ( sDataSourceName ) ;
if ( aParser . GetProtocol ( ) ! = INET_PROT_NOT_VALID )
sDataSourceName = aParser . getBase ( INetURLObject : : LAST_SEGMENT , true , INetURLObject : : DECODE_WITH_CHARSET ) ;
sInfo . SearchAndReplaceAllAscii ( " $name$ " , sDataSourceName ) ;
SQLContext aContext ;
aContext . Message = sInfo ;
aContext . NextException = aError . get ( ) ;
impl_displaySQLError_nothrow ( aContext ) ;
}
return m_xRowSetConnection . is ( ) ;
}
//------------------------------------------------------------------------
void FormComponentPropertyHandler : : impl_describeCursorSource_nothrow ( LineDescriptor & _out_rProperty , const Reference < XPropertyControlFactory > & _rxControlFactory ) const
{
try
{
WaitCursor aWaitCursor ( impl_getDefaultDialogParent_nothrow ( ) ) ;
////////////////////////////////////////////////////////////
// Setzen der UI-Daten
_out_rProperty . DisplayName = m_pInfoService - > getPropertyTranslation ( PROPERTY_ID_COMMAND ) ;
_out_rProperty . HelpURL = HelpIdUrl : : getHelpURL ( m_pInfoService - > getPropertyHelpId ( PROPERTY_ID_COMMAND ) ) ;
_out_rProperty . PrimaryButtonId = UID_PROP_DLG_SQLCOMMAND ;
////////////////////////////////////////////////////////////
sal_Int32 nCommandType = CommandType : : COMMAND ;
impl_getPropertyValue_throw ( PROPERTY_COMMANDTYPE ) > > = nCommandType ;
switch ( nCommandType )
{
case CommandType : : TABLE :
case CommandType : : QUERY :
{
: : std : : vector < : : rtl : : OUString > aNames ;
if ( impl_ensureRowsetConnection_nothrow ( ) )
{
if ( nCommandType = = CommandType : : TABLE )
impl_fillTableNames_throw ( aNames ) ;
else
impl_fillQueryNames_throw ( aNames ) ;
}
2006-12-13 15:57:02 +00:00
_out_rProperty . Control = PropertyHandlerHelper : : createComboBoxControl ( _rxControlFactory , aNames , sal_False , sal_True ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
break ;
default :
_out_rProperty . Control = _rxControlFactory - > createPropertyControl ( PropertyControlType : : MultiLineTextField , sal_False ) ;
break ;
}
}
catch ( Exception & )
{
2008-11-10 15:06:12 +00:00
DBG_ERROR ( " FormComponentPropertyHandler::impl_describeCursorSource_nothrow: caught an exception ! " ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
}
//------------------------------------------------------------------------
void FormComponentPropertyHandler : : impl_fillTableNames_throw ( : : std : : vector < : : rtl : : OUString > & _out_rNames ) const
{
OSL_PRECOND ( m_xRowSetConnection . is ( ) , " FormComponentPropertyHandler::impl_fillTableNames_throw: need a connection! " ) ;
_out_rNames . resize ( 0 ) ;
Reference < XTablesSupplier > xSupplyTables ( m_xRowSetConnection , UNO_QUERY ) ;
Reference < XNameAccess > xTableNames ;
if ( xSupplyTables . is ( ) )
xTableNames = xSupplyTables - > getTables ( ) ;
DBG_ASSERT ( xTableNames . is ( ) , " FormComponentPropertyHandler::impl_fillTableNames_throw: no way to obtain the tables of the connection! " ) ;
if ( ! xTableNames . is ( ) )
return ;
Sequence < : : rtl : : OUString > aTableNames = xTableNames - > getElementNames ( ) ;
sal_uInt32 nCount = aTableNames . getLength ( ) ;
const : : rtl : : OUString * pTableNames = aTableNames . getConstArray ( ) ;
for ( sal_uInt32 i = 0 ; i < nCount ; + + i , + + pTableNames )
_out_rNames . push_back ( * pTableNames ) ;
}
//------------------------------------------------------------------------
void FormComponentPropertyHandler : : impl_fillQueryNames_throw ( : : std : : vector < : : rtl : : OUString > & _out_rNames ) const
{
OSL_PRECOND ( m_xRowSetConnection . is ( ) , " FormComponentPropertyHandler::impl_fillQueryNames_throw: need a connection! " ) ;
_out_rNames . resize ( 0 ) ;
Reference < XQueriesSupplier > xSupplyQueries ( m_xRowSetConnection , UNO_QUERY ) ;
Reference < XNameAccess > xQueryNames ;
if ( xSupplyQueries . is ( ) )
xQueryNames = xSupplyQueries - > getQueries ( ) ;
DBG_ASSERT ( xQueryNames . is ( ) , " FormComponentPropertyHandler::impl_fillQueryNames_throw: no way to obtain the queries of the connection! " ) ;
if ( ! xQueryNames . is ( ) )
return ;
Sequence < : : rtl : : OUString > aQueryNames = xQueryNames - > getElementNames ( ) ;
sal_uInt32 nCount = aQueryNames . getLength ( ) ;
const : : rtl : : OUString * pQueryNames = aQueryNames . getConstArray ( ) ;
for ( sal_uInt32 i = 0 ; i < nCount ; i + + , + + pQueryNames )
_out_rNames . push_back ( * pQueryNames ) ;
}
//------------------------------------------------------------------------
void FormComponentPropertyHandler : : impl_describeListSourceUI_throw ( LineDescriptor & _out_rDescriptor , const Reference < XPropertyControlFactory > & _rxControlFactory ) const
{
OSL_PRECOND ( m_xComponent . is ( ) , " FormComponentPropertyHandler::impl_describeListSourceUI_throw: no component! " ) ;
////////////////////////////////////////////////////////////
// Auslesen des ListSourceTypes
Any aListSourceType ( m_xComponent - > getPropertyValue ( PROPERTY_LISTSOURCETYPE ) ) ;
sal_Int32 nListSourceType = ListSourceType_VALUELIST ;
: : cppu : : enum2int ( nListSourceType , aListSourceType ) ;
_out_rDescriptor . DisplayName = m_pInfoService - > getPropertyTranslation ( PROPERTY_ID_LISTSOURCE ) ;
_out_rDescriptor . HelpURL = HelpIdUrl : : getHelpURL ( m_pInfoService - > getPropertyHelpId ( PROPERTY_ID_LISTSOURCE ) ) ;
////////////////////////////////////////////////////////////
// Enums setzen
switch ( nListSourceType )
{
case ListSourceType_VALUELIST :
_out_rDescriptor . Control = _rxControlFactory - > createPropertyControl ( PropertyControlType : : StringListField , sal_False ) ;
break ;
case ListSourceType_TABLEFIELDS :
case ListSourceType_TABLE :
case ListSourceType_QUERY :
{
: : std : : vector < : : rtl : : OUString > aListEntries ;
if ( impl_ensureRowsetConnection_nothrow ( ) )
{
if ( nListSourceType = = ListSourceType_QUERY )
impl_fillQueryNames_throw ( aListEntries ) ;
else
impl_fillTableNames_throw ( aListEntries ) ;
}
2006-12-13 15:57:02 +00:00
_out_rDescriptor . Control = PropertyHandlerHelper : : createComboBoxControl ( _rxControlFactory , aListEntries , sal_False , sal_False ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
break ;
2007-11-21 15:21:57 +00:00
case ListSourceType_SQL :
case ListSourceType_SQLPASSTHROUGH :
impl_ensureRowsetConnection_nothrow ( ) ;
_out_rDescriptor . HasPrimaryButton = m_xRowSetConnection . is ( ) ;
break ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_dialogListSelection_nothrow ( const : : rtl : : OUString & _rProperty , : : osl : : ClearableMutexGuard & _rClearBeforeDialog ) const
{
OSL_PRECOND ( m_pInfoService . get ( ) , " FormComponentPropertyHandler::impl_dialogListSelection_nothrow: no property meta data! " ) ;
String sPropertyUIName ( m_pInfoService - > getPropertyTranslation ( m_pInfoService - > getPropertyId ( _rProperty ) ) ) ;
ListSelectionDialog aDialog ( impl_getDefaultDialogParent_nothrow ( ) , m_xComponent , _rProperty , sPropertyUIName ) ;
_rClearBeforeDialog . clear ( ) ;
return ( RET_OK = = aDialog . Execute ( ) ) ;
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_dialogFilterOrSort_nothrow ( bool _bFilter , : : rtl : : OUString & _out_rSelectedClause , : : osl : : ClearableMutexGuard & _rClearBeforeDialog ) const
{
OSL_PRECOND ( Reference < XRowSet > ( m_xComponent , UNO_QUERY ) . is ( ) ,
" FormComponentPropertyHandler::impl_dialogFilterOrSort_nothrow: to be called for forms only! " ) ;
_out_rSelectedClause = : : rtl : : OUString ( ) ;
bool bSuccess = false ;
SQLExceptionInfo aErrorInfo ;
try
{
if ( ! impl_ensureRowsetConnection_nothrow ( ) )
return false ;
// get a composer for the statement which the form is currently based on
Reference < XSingleSelectQueryComposer > xComposer ( : : dbtools : : getCurrentSettingsComposer ( m_xComponent , m_aContext . getLegacyServiceFactory ( ) ) ) ;
OSL_ENSURE ( xComposer . is ( ) , " FormComponentPropertyHandler::impl_dialogFilterOrSort_nothrow: could not obtain a composer! " ) ;
if ( ! xComposer . is ( ) )
return false ;
: : rtl : : OUString sPropertyUIName ( m_pInfoService - > getPropertyTranslation ( _bFilter ? PROPERTY_ID_FILTER : PROPERTY_ID_SORT ) ) ;
const sal_Char * pAsciiServiceName = _bFilter ? " com.sun.star.sdb.FilterDialog " : " com.sun.star.sdb.OrderDialog " ;
// create the dialog
Reference < XExecutableDialog > xDialog ;
if ( ! m_aContext . createComponent ( pAsciiServiceName , xDialog ) )
{
ShowServiceNotAvailableError ( impl_getDefaultDialogParent_nothrow ( ) , : : rtl : : OUString : : createFromAscii ( pAsciiServiceName ) , sal_True ) ;
return false ;
}
// initialize the dialog
Reference < XPropertySet > xDialogProps ( xDialog , UNO_QUERY_THROW ) ;
xDialogProps - > setPropertyValue ( : : rtl : : OUString ( RTL_CONSTASCII_USTRINGPARAM ( " QueryComposer " ) ) , makeAny ( xComposer ) ) ;
xDialogProps - > setPropertyValue ( : : rtl : : OUString ( RTL_CONSTASCII_USTRINGPARAM ( " RowSet " ) ) , makeAny ( m_xComponent ) ) ;
xDialogProps - > setPropertyValue ( : : rtl : : OUString ( RTL_CONSTASCII_USTRINGPARAM ( " ParentWindow " ) ) , makeAny ( VCLUnoHelper : : GetInterface ( impl_getDefaultDialogParent_nothrow ( ) ) ) ) ;
xDialogProps - > setPropertyValue ( : : rtl : : OUString ( RTL_CONSTASCII_USTRINGPARAM ( " Title " ) ) , makeAny ( sPropertyUIName ) ) ;
_rClearBeforeDialog . clear ( ) ;
bSuccess = ( xDialog - > execute ( ) ! = 0 ) ;
if ( bSuccess )
_out_rSelectedClause = _bFilter ? xComposer - > getFilter ( ) : xComposer - > getOrder ( ) ;
}
catch ( SQLContext & e ) { aErrorInfo = e ; }
catch ( SQLWarning & e ) { aErrorInfo = e ; }
catch ( SQLException & e ) { aErrorInfo = e ; }
catch ( const Exception & )
{
OSL_ENSURE ( sal_False , " FormComponentPropertyHandler::impl_dialogFilterOrSort_nothrow: caught an exception! " ) ;
}
if ( aErrorInfo . isValid ( ) )
impl_displaySQLError_nothrow ( aErrorInfo ) ;
return bSuccess ;
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_dialogLinkedFormFields_nothrow ( : : osl : : ClearableMutexGuard & _rClearBeforeDialog ) const
{
Reference < XForm > xDetailForm ( m_xComponent , UNO_QUERY ) ;
Reference < XForm > xMasterForm ( m_xObjectParent , UNO_QUERY ) ;
2008-03-05 16:10:03 +00:00
uno : : Reference < beans : : XPropertySet > xMasterProp ( m_xObjectParent , uno : : UNO_QUERY ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
OSL_PRECOND ( xDetailForm . is ( ) & & xMasterForm . is ( ) , " FormComponentPropertyHandler::impl_dialogLinkedFormFields_nothrow: no forms! " ) ;
if ( ! xDetailForm . is ( ) | | ! xMasterForm . is ( ) )
return false ;
2008-03-05 16:10:03 +00:00
FormLinkDialog aDialog ( impl_getDefaultDialogParent_nothrow ( ) , m_xComponent , xMasterProp , m_aContext . getLegacyServiceFactory ( ) ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
_rClearBeforeDialog . clear ( ) ;
return ( RET_OK = = aDialog . Execute ( ) ) ;
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_dialogFormatting_nothrow ( Any & _out_rNewValue , : : osl : : ClearableMutexGuard & _rClearBeforeDialog ) const
{
bool bChanged = false ;
try
{
// create the itemset for the dialog
SfxItemSet aCoreSet ( SFX_APP ( ) - > GetPool ( ) ,
SID_ATTR_NUMBERFORMAT_VALUE , SID_ATTR_NUMBERFORMAT_VALUE ,
SID_ATTR_NUMBERFORMAT_INFO , SID_ATTR_NUMBERFORMAT_INFO ,
0 ) ; // ripped this somewhere ... don't understand it :(
// get the number formats supplier
Reference < XNumberFormatsSupplier > xSupplier ;
m_xComponent - > getPropertyValue ( PROPERTY_FORMATSSUPPLIER ) > > = xSupplier ;
DBG_ASSERT ( xSupplier . is ( ) , " FormComponentPropertyHandler::impl_dialogFormatting_nothrow: invalid call ! " ) ;
Reference < XUnoTunnel > xTunnel ( xSupplier , UNO_QUERY_THROW ) ;
SvNumberFormatsSupplierObj * pSupplier =
reinterpret_cast < SvNumberFormatsSupplierObj * > ( xTunnel - > getSomething ( SvNumberFormatsSupplierObj : : getUnoTunnelId ( ) ) ) ;
DBG_ASSERT ( pSupplier ! = NULL , " FormComponentPropertyHandler::impl_dialogFormatting_nothrow: invalid call ! " ) ;
sal_Int32 nFormatKey = 0 ;
impl_getPropertyValue_throw ( PROPERTY_FORMATKEY ) > > = nFormatKey ;
aCoreSet . Put ( SfxUInt32Item ( SID_ATTR_NUMBERFORMAT_VALUE , nFormatKey ) ) ;
SvNumberFormatter * pFormatter = pSupplier - > GetNumberFormatter ( ) ;
2007-11-20 18:52:21 +00:00
double dPreviewVal = OFormatSampleControl : : getPreviewValue ( pFormatter , nFormatKey ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
SvxNumberInfoItem aFormatter ( pFormatter , dPreviewVal , SID_ATTR_NUMBERFORMAT_INFO ) ;
aCoreSet . Put ( aFormatter ) ;
// a tab dialog with a single page
: : std : : auto_ptr < SfxSingleTabDialog > pDialog ( new SfxSingleTabDialog ( impl_getDefaultDialogParent_nothrow ( ) , aCoreSet , 0 ) ) ;
SvxAbstractDialogFactory * pFact = SvxAbstractDialogFactory : : Create ( ) ;
DBG_ASSERT ( pFact , " CreateFactory fail! " ) ;
: : CreateTabPage fnCreatePage = pFact - > GetTabPageCreatorFunc ( RID_SVXPAGE_NUMBERFORMAT ) ;
if ( ! fnCreatePage )
throw RuntimeException ( ) ; // caught below
SfxTabPage * pPage = ( * fnCreatePage ) ( pDialog . get ( ) , aCoreSet ) ;
pDialog - > SetTabPage ( pPage ) ;
_rClearBeforeDialog . clear ( ) ;
if ( RET_OK = = pDialog - > Execute ( ) )
{
const SfxItemSet * pResult = pDialog - > GetOutputItemSet ( ) ;
const SfxPoolItem * pItem = pResult - > GetItem ( SID_ATTR_NUMBERFORMAT_INFO ) ;
const SvxNumberInfoItem * pInfoItem = dynamic_cast < const SvxNumberInfoItem * > ( pItem ) ;
if ( pInfoItem & & pInfoItem - > GetDelCount ( ) )
{
const sal_uInt32 * pDeletedKeys = pInfoItem - > GetDelArray ( ) ;
for ( sal_uInt16 i = 0 ; i < pInfoItem - > GetDelCount ( ) ; + + i , + + pDeletedKeys )
pFormatter - > DeleteEntry ( * pDeletedKeys ) ;
}
pItem = NULL ;
if ( SFX_ITEM_SET = = pResult - > GetItemState ( SID_ATTR_NUMBERFORMAT_VALUE , sal_False , & pItem ) )
{
_out_rNewValue < < = ( sal_Int32 ) ( static_cast < const SfxUInt32Item * > ( pItem ) - > GetValue ( ) ) ;
bChanged = true ;
}
}
}
catch ( const Exception & )
{
OSL_ENSURE ( sal_False , " FormComponentPropertyHandler::impl_dialogFormatting_nothrow: : caught an exception! " ) ;
}
return bChanged ;
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_browseForImage_nothrow ( Any & _out_rNewValue , : : osl : : ClearableMutexGuard & _rClearBeforeDialog ) const
{
2008-12-01 12:31:27 +00:00
bool bIsLink = true ; // reflect the legacy behavior
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
: : rtl : : OUString aStrTrans = m_pInfoService - > getPropertyTranslation ( PROPERTY_ID_IMAGE_URL ) ;
: : sfx2 : : FileDialogHelper aFileDlg ( SFXWB_GRAPHIC ) ;
aFileDlg . SetTitle ( aStrTrans ) ;
2008-12-01 12:31:27 +00:00
// non-linked images ( e.g. those located in the document
// stream ) cannot *currently* be handled by openoffice basic dialogs.
bool bHandleNonLink = ( m_eComponentClass = = eFormControl ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
Reference < XFilePickerControlAccess > xController ( aFileDlg . GetFilePicker ( ) , UNO_QUERY ) ;
DBG_ASSERT ( xController . is ( ) , " FormComponentPropertyHandler::impl_browseForImage_nothrow: missing the controller interface on the file picker! " ) ;
if ( xController . is ( ) )
{
// do a preview by default
xController - > setValue ( ExtendedFilePickerElementIds : : CHECKBOX_PREVIEW , 0 , : : cppu : : bool2any ( sal_True ) ) ;
2008-12-01 12:31:27 +00:00
xController - > setValue ( ExtendedFilePickerElementIds : : CHECKBOX_LINK , 0 , : : cppu : : bool2any ( bIsLink ) ) ;
xController - > enableControl ( ExtendedFilePickerElementIds : : CHECKBOX_LINK , bHandleNonLink ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
: : rtl : : OUString sCurValue ;
OSL_VERIFY ( impl_getPropertyValue_throw ( PROPERTY_IMAGE_URL ) > > = sCurValue ) ;
2008-12-01 12:31:27 +00:00
if ( sCurValue . getLength ( ) ! = 0 & & sCurValue . compareToAscii ( GRAPHOBJ_URLPREFIX , RTL_CONSTASCII_LENGTH ( GRAPHOBJ_URLPREFIX ) ) ! = 0 )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
aFileDlg . SetDisplayDirectory ( sCurValue ) ;
// TODO: need to set the display directory _and_ the default name
}
_rClearBeforeDialog . clear ( ) ;
bool bSuccess = ( 0 = = aFileDlg . Execute ( ) ) ;
if ( bSuccess )
2008-12-01 12:31:27 +00:00
{
if ( bHandleNonLink & & xController . is ( ) )
{
xController - > getValue ( ExtendedFilePickerElementIds : : CHECKBOX_LINK , 0 ) > > = bIsLink ;
}
if ( ! bIsLink )
{
Graphic aGraphic ;
aFileDlg . GetGraphic ( aGraphic ) ;
Reference < graphic : : XGraphicObject > xGrfObj = graphic : : GraphicObject : : create ( m_aContext . getUNOContext ( ) ) ;
xGrfObj - > setGraphic ( aGraphic . GetXGraphic ( ) ) ;
_out_rNewValue < < = xGrfObj ;
}
else
_out_rNewValue < < = ( : : rtl : : OUString ) aFileDlg . GetPath ( ) ;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
return bSuccess ;
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_browseForTargetURL_nothrow ( Any & _out_rNewValue , : : osl : : ClearableMutexGuard & _rClearBeforeDialog ) const
{
: : sfx2 : : FileDialogHelper aFileDlg ( WB_3DLOOK ) ;
: : rtl : : OUString sURL ;
OSL_VERIFY ( impl_getPropertyValue_throw ( PROPERTY_TARGET_URL ) > > = sURL ) ;
INetURLObject aParser ( sURL ) ;
if ( INET_PROT_FILE = = aParser . GetProtocol ( ) )
// set the initial directory only for file-URLs. Everything else
// is considered to be potentially expensive
// 106126 - 2002/12/10 - fs@openoffice.org
aFileDlg . SetDisplayDirectory ( sURL ) ;
_rClearBeforeDialog . clear ( ) ;
bool bSuccess = ( 0 = = aFileDlg . Execute ( ) ) ;
if ( bSuccess )
_out_rNewValue < < = ( : : rtl : : OUString ) aFileDlg . GetPath ( ) ;
return bSuccess ;
}
//------------------------------------------------------------------------
2006-03-31 11:19:30 +00:00
bool FormComponentPropertyHandler : : impl_executeFontDialog_nothrow ( Any & _out_rNewValue , : : osl : : ClearableMutexGuard & _rClearBeforeDialog ) const
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
bool bSuccess = false ;
// create an item set for use with the dialog
SfxItemSet * pSet = NULL ;
SfxItemPool * pPool = NULL ;
SfxPoolItem * * pDefaults = NULL ;
ControlCharacterDialog : : createItemSet ( pSet , pPool , pDefaults ) ;
ControlCharacterDialog : : translatePropertiesToItems ( m_xComponent , pSet ) ;
{ // do this in an own block. The dialog needs to be destroyed before we call
// destroyItemSet
ControlCharacterDialog aDlg ( impl_getDefaultDialogParent_nothrow ( ) , * pSet ) ;
_rClearBeforeDialog . clear ( ) ;
if ( RET_OK = = aDlg . Execute ( ) )
{
const SfxItemSet * pOut = aDlg . GetOutputItemSet ( ) ;
2006-03-31 11:19:30 +00:00
if ( pOut )
{
Sequence < NamedValue > aFontPropertyValues ;
ControlCharacterDialog : : translateItemsToProperties ( * pOut , aFontPropertyValues ) ;
_out_rNewValue < < = aFontPropertyValues ;
bSuccess = true ;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
}
ControlCharacterDialog : : destroyItemSet ( pSet , pPool , pDefaults ) ;
return bSuccess ;
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_browseForDatabaseDocument_throw ( Any & _out_rNewValue , : : osl : : ClearableMutexGuard & _rClearBeforeDialog ) const
{
2008-12-09 07:25:38 +00:00
: : sfx2 : : FileDialogHelper aFileDlg ( WB_3DLOOK | WB_OPEN , : : String : : CreateFromAscii ( " sdatabase " ) ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
: : rtl : : OUString sDataSource ;
OSL_VERIFY ( impl_getPropertyValue_throw ( PROPERTY_DATASOURCE ) > > = sDataSource ) ;
INetURLObject aParser ( sDataSource ) ;
if ( INET_PROT_FILE = = aParser . GetProtocol ( ) )
// set the initial directory only for file-URLs. Everything else
// is considered to be potentially expensive
// 106126 - 2002/12/10 - fs@openoffice.org
aFileDlg . SetDisplayDirectory ( sDataSource ) ;
const String s_sDatabaseType = String : : CreateFromAscii ( " StarOffice XML (Base) " ) ;
const SfxFilter * pFilter = SfxFilter : : GetFilterByName ( s_sDatabaseType ) ;
OSL_ENSURE ( pFilter , " Filter: StarOffice XML (Base) could not be found! " ) ;
if ( pFilter )
{
2008-12-09 07:25:38 +00:00
aFileDlg . SetCurrentFilter ( pFilter - > GetUIName ( ) ) ;
//aFileDlg.AddFilter(pFilter->GetFilterName(),pFilter->GetDefaultExtension());
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
_rClearBeforeDialog . clear ( ) ;
bool bSuccess = ( 0 = = aFileDlg . Execute ( ) ) ;
if ( bSuccess )
_out_rNewValue < < = ( : : rtl : : OUString ) aFileDlg . GetPath ( ) ;
return bSuccess ;
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_dialogColorChooser_throw ( sal_Int32 _nColorPropertyId , Any & _out_rNewValue , : : osl : : ClearableMutexGuard & _rClearBeforeDialog ) const
{
sal_Int32 nColor = 0 ;
OSL_VERIFY ( impl_getPropertyValue_throw ( impl_getPropertyNameFromId_nothrow ( _nColorPropertyId ) ) > > = nColor ) ;
: : Color aColor ( nColor ) ;
SvColorDialog aColorDlg ( impl_getDefaultDialogParent_nothrow ( ) ) ;
aColorDlg . SetColor ( aColor ) ;
_rClearBeforeDialog . clear ( ) ;
if ( ! aColorDlg . Execute ( ) )
return false ;
aColor = aColorDlg . GetColor ( ) ;
nColor = aColor . GetColor ( ) ;
_out_rNewValue < < = ( sal_Int32 ) nColor ;
return true ;
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_dialogChooseLabelControl_nothrow ( Any & _out_rNewValue , : : osl : : ClearableMutexGuard & _rClearBeforeDialog ) const
{
OSelectLabelDialog dlgSelectLabel ( impl_getDefaultDialogParent_nothrow ( ) , m_xComponent ) ;
_rClearBeforeDialog . clear ( ) ;
bool bSuccess = ( RET_OK = = dlgSelectLabel . Execute ( ) ) ;
if ( bSuccess )
_out_rNewValue < < = dlgSelectLabel . GetSelected ( ) ;
return bSuccess ;
}
//------------------------------------------------------------------------
Reference < XControlContainer > FormComponentPropertyHandler : : impl_getContextControlContainer_nothrow ( ) const
{
Reference < XControlContainer > xControlContext (
m_aContext . getContextValueByAsciiName ( " ControlContext " ) ,
UNO_QUERY ) ;
return xControlContext ;
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_dialogChangeTabOrder_nothrow ( : : osl : : ClearableMutexGuard & _rClearBeforeDialog ) const
{
OSL_PRECOND ( impl_getContextControlContainer_nothrow ( ) . is ( ) , " FormComponentPropertyHandler::impl_dialogChangeTabOrder_nothrow: invalid control context! " ) ;
Reference < XTabControllerModel > xTabControllerModel ( impl_getRowSet_nothrow ( ) , UNO_QUERY ) ;
TabOrderDialog aDialog (
impl_getDefaultDialogParent_nothrow ( ) ,
xTabControllerModel ,
impl_getContextControlContainer_nothrow ( ) ,
m_aContext . getLegacyServiceFactory ( )
) ;
_rClearBeforeDialog . clear ( ) ;
return ( RET_OK = = aDialog . Execute ( ) ) ;
}
//------------------------------------------------------------------------
2007-11-21 15:21:57 +00:00
namespace
{
//--------------------------------------------------------------------
//- ISQLCommandPropertyUI
//--------------------------------------------------------------------
class ISQLCommandPropertyUI : public ISQLCommandAdapter
{
public :
/** returns the empty-string-terminated list of names of properties
whose UI is to be disabled while the SQL command property is
being edited .
*/
virtual : : rtl : : OUString * getPropertiesToDisable ( ) = 0 ;
} ;
//--------------------------------------------------------------------
//- SQLCommandPropertyUI
//--------------------------------------------------------------------
class SQLCommandPropertyUI : public ISQLCommandPropertyUI
{
protected :
SQLCommandPropertyUI ( const Reference < XPropertySet > & _rxObject )
: m_xObject ( _rxObject )
{
if ( ! m_xObject . is ( ) )
throw NullPointerException ( ) ;
}
virtual oslInterlockedCount SAL_CALL acquire ( )
{
return osl_incrementInterlockedCount ( & m_refCount ) ;
}
virtual oslInterlockedCount SAL_CALL release ( )
{
if ( 0 = = osl_decrementInterlockedCount ( & m_refCount ) )
{
delete this ;
return 0 ;
}
return m_refCount ;
}
protected :
Reference < XPropertySet > m_xObject ;
private :
oslInterlockedCount m_refCount ;
} ;
//--------------------------------------------------------------------
//- FormSQLCommandUI - declaration
//--------------------------------------------------------------------
class FormSQLCommandUI : public SQLCommandPropertyUI
{
public :
FormSQLCommandUI ( const Reference < XPropertySet > & _rxForm ) ;
// ISQLCommandAdapter
virtual : : rtl : : OUString getSQLCommand ( ) const ;
virtual sal_Bool getEscapeProcessing ( ) const ;
virtual void setSQLCommand ( const : : rtl : : OUString & _rCommand ) const ;
virtual void setEscapeProcessing ( const sal_Bool _bEscapeProcessing ) const ;
// ISQLCommandPropertyUI
virtual : : rtl : : OUString * getPropertiesToDisable ( ) ;
} ;
//--------------------------------------------------------------------
//- FormSQLCommandUI - implementation
//--------------------------------------------------------------------
//....................................................................
FormSQLCommandUI : : FormSQLCommandUI ( const Reference < XPropertySet > & _rxForm )
: SQLCommandPropertyUI ( _rxForm )
{
}
//....................................................................
: : rtl : : OUString FormSQLCommandUI : : getSQLCommand ( ) const
{
: : rtl : : OUString sCommand ;
OSL_VERIFY ( m_xObject - > getPropertyValue ( PROPERTY_COMMAND ) > > = sCommand ) ;
return sCommand ;
}
//....................................................................
sal_Bool FormSQLCommandUI : : getEscapeProcessing ( ) const
{
sal_Bool bEscapeProcessing ( sal_False ) ;
OSL_VERIFY ( m_xObject - > getPropertyValue ( PROPERTY_ESCAPE_PROCESSING ) > > = bEscapeProcessing ) ;
return bEscapeProcessing ;
}
//....................................................................
void FormSQLCommandUI : : setSQLCommand ( const : : rtl : : OUString & _rCommand ) const
{
m_xObject - > setPropertyValue ( PROPERTY_COMMAND , makeAny ( _rCommand ) ) ;
}
//....................................................................
void FormSQLCommandUI : : setEscapeProcessing ( const sal_Bool _bEscapeProcessing ) const
{
m_xObject - > setPropertyValue ( PROPERTY_ESCAPE_PROCESSING , makeAny ( _bEscapeProcessing ) ) ;
}
//....................................................................
: : rtl : : OUString * FormSQLCommandUI : : getPropertiesToDisable ( )
{
static : : rtl : : OUString s_aCommandProps [ ] = {
PROPERTY_DATASOURCE ,
PROPERTY_COMMAND ,
PROPERTY_COMMANDTYPE ,
PROPERTY_ESCAPE_PROCESSING ,
: : rtl : : OUString ( )
} ;
return s_aCommandProps ;
}
//--------------------------------------------------------------------
//- ValueListCommandUI - declaration
//--------------------------------------------------------------------
class ValueListCommandUI : public SQLCommandPropertyUI
{
public :
ValueListCommandUI ( const Reference < XPropertySet > & _rxListOrCombo ) ;
// ISQLCommandAdapter
virtual : : rtl : : OUString getSQLCommand ( ) const ;
virtual sal_Bool getEscapeProcessing ( ) const ;
virtual void setSQLCommand ( const : : rtl : : OUString & _rCommand ) const ;
virtual void setEscapeProcessing ( const sal_Bool _bEscapeProcessing ) const ;
// ISQLCommandPropertyUI
virtual : : rtl : : OUString * getPropertiesToDisable ( ) ;
private :
mutable bool m_bPropertyValueIsList ;
} ;
//--------------------------------------------------------------------
//- ValueListCommandUI - implementation
//--------------------------------------------------------------------
//....................................................................
ValueListCommandUI : : ValueListCommandUI ( const Reference < XPropertySet > & _rxListOrCombo )
: SQLCommandPropertyUI ( _rxListOrCombo )
, m_bPropertyValueIsList ( false )
{
}
//....................................................................
: : rtl : : OUString ValueListCommandUI : : getSQLCommand ( ) const
{
: : rtl : : OUString sValue ;
m_bPropertyValueIsList = false ;
// for combo boxes, the property is a mere string
Any aValue ( m_xObject - > getPropertyValue ( PROPERTY_LISTSOURCE ) ) ;
if ( aValue > > = sValue )
return sValue ;
Sequence < : : rtl : : OUString > aValueList ;
if ( aValue > > = aValueList )
{
m_bPropertyValueIsList = true ;
if ( aValueList . getLength ( ) )
sValue = aValueList [ 0 ] ;
return sValue ;
}
OSL_ENSURE ( false , " ValueListCommandUI::getSQLCommand: unexpected property type! " ) ;
return sValue ;
}
//....................................................................
sal_Bool ValueListCommandUI : : getEscapeProcessing ( ) const
{
enum ListSourceType eType ( ListSourceType_SQL ) ;
OSL_VERIFY ( m_xObject - > getPropertyValue ( PROPERTY_LISTSOURCETYPE ) > > = eType ) ;
OSL_ENSURE ( ( eType = = ListSourceType_SQL ) | | ( eType = = ListSourceType_SQLPASSTHROUGH ) ,
" ValueListCommandUI::getEscapeProcessing: unexpected list source type! " ) ;
return ( eType = = ListSourceType_SQL ) ;
}
//....................................................................
void ValueListCommandUI : : setSQLCommand ( const : : rtl : : OUString & _rCommand ) const
{
Any aValue ;
if ( m_bPropertyValueIsList )
aValue < < = Sequence < : : rtl : : OUString > ( & _rCommand , 1 ) ;
else
aValue < < = _rCommand ;
m_xObject - > setPropertyValue ( PROPERTY_LISTSOURCE , aValue ) ;
}
//....................................................................
void ValueListCommandUI : : setEscapeProcessing ( const sal_Bool _bEscapeProcessing ) const
{
m_xObject - > setPropertyValue ( PROPERTY_LISTSOURCETYPE , makeAny (
_bEscapeProcessing ? ListSourceType_SQL : ListSourceType_SQLPASSTHROUGH ) ) ;
}
//....................................................................
: : rtl : : OUString * ValueListCommandUI : : getPropertiesToDisable ( )
{
static : : rtl : : OUString s_aListSourceProps [ ] = {
PROPERTY_LISTSOURCETYPE ,
PROPERTY_LISTSOURCE ,
: : rtl : : OUString ( )
} ;
return s_aListSourceProps ;
}
}
//------------------------------------------------------------------------
bool FormComponentPropertyHandler : : impl_doDesignSQLCommand_nothrow ( const Reference < XObjectInspectorUI > & _rxInspectorUI , PropertyId _nDesignForProperty )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
try
{
if ( m_xCommandDesigner . is ( ) )
{
if ( m_xCommandDesigner - > isActive ( ) )
{
m_xCommandDesigner - > raise ( ) ;
return true ;
}
m_xCommandDesigner - > dispose ( ) ;
m_xCommandDesigner . set ( NULL ) ;
}
if ( ! impl_ensureRowsetConnection_nothrow ( ) )
return false ;
2007-11-21 15:21:57 +00:00
Reference < XPropertySet > xComponentProperties ( m_xComponent , UNO_QUERY_THROW ) ;
: : rtl : : Reference < ISQLCommandPropertyUI > xCommandUI ;
switch ( _nDesignForProperty )
{
case PROPERTY_ID_COMMAND :
xCommandUI = new FormSQLCommandUI ( xComponentProperties ) ;
break ;
case PROPERTY_ID_LISTSOURCE :
xCommandUI = new ValueListCommandUI ( xComponentProperties ) ;
break ;
default :
OSL_ENSURE ( false , " FormComponentPropertyHandler::OnDesignerClosed: invalid property id! " ) ;
return false ;
}
m_xCommandDesigner . set ( new SQLCommandDesigner ( m_aContext . getUNOContext ( ) , xCommandUI . get ( ) , m_xRowSetConnection , LINK ( this , FormComponentPropertyHandler , OnDesignerClosed ) ) ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
DBG_ASSERT ( _rxInspectorUI . is ( ) , " FormComponentPropertyHandler::OnDesignerClosed: no access to the property browser ui! " ) ;
if ( m_xCommandDesigner - > isActive ( ) & & _rxInspectorUI . is ( ) )
{
m_xBrowserUI = _rxInspectorUI ;
2007-11-21 15:21:57 +00:00
// disable everything which would affect this property
const : : rtl : : OUString * pToDisable = xCommandUI - > getPropertiesToDisable ( ) ;
while ( pToDisable - > getLength ( ) )
{
m_xBrowserUI - > enablePropertyUIElements ( * pToDisable + + , PropertyLineElement : : All , sal_False ) ;
}
// but enable the browse button for the property itself - so it can be used to raise the query designer
: : rtl : : OUString sPropertyName ( impl_getPropertyNameFromId_nothrow ( _nDesignForProperty ) ) ;
m_xBrowserUI - > enablePropertyUIElements ( sPropertyName , PropertyLineElement : : PrimaryButton , sal_True ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
}
catch ( const Exception & )
{
2007-11-21 15:21:57 +00:00
DBG_UNHANDLED_EXCEPTION ( ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
return m_xCommandDesigner . is ( ) ;
}
//------------------------------------------------------------------------
2006-07-26 06:56:33 +00:00
IMPL_LINK ( FormComponentPropertyHandler , OnDesignerClosed , void * , /*NOTINTERESTEDIN*/ )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
2007-11-21 15:21:57 +00:00
OSL_ENSURE ( m_xBrowserUI . is ( ) & & m_xCommandDesigner . is ( ) , " FormComponentPropertyHandler::OnDesignerClosed: too many NULLs! " ) ;
if ( m_xBrowserUI . is ( ) & & m_xCommandDesigner . is ( ) )
{
try
{
: : rtl : : Reference < ISQLCommandPropertyUI > xCommandUI (
dynamic_cast < ISQLCommandPropertyUI * > ( m_xCommandDesigner - > getPropertyAdapter ( ) . get ( ) ) ) ;
if ( ! xCommandUI . is ( ) )
throw NullPointerException ( ) ;
const : : rtl : : OUString * pToEnable = xCommandUI - > getPropertiesToDisable ( ) ;
while ( pToEnable - > getLength ( ) )
{
m_xBrowserUI - > enablePropertyUIElements ( * pToEnable + + , PropertyLineElement : : All , sal_True ) ;
}
}
catch ( const Exception & )
{
DBG_UNHANDLED_EXCEPTION ( ) ;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
return 0L ;
}
//------------------------------------------------------------------------
2007-07-06 07:48:27 +00:00
bool FormComponentPropertyHandler : : impl_hasValidDataSourceSignature_nothrow ( const Reference < XPropertySet > & _xFormProperties , bool _bAllowEmptyDataSourceName ) SAL_THROW ( ( ) )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
bool bHas = false ;
2007-07-06 07:48:27 +00:00
if ( _xFormProperties . is ( ) )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
2007-07-06 07:48:27 +00:00
try
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
2007-07-06 07:48:27 +00:00
: : rtl : : OUString sPropertyValue ;
// first, we need the name of an existent data source
if ( _xFormProperties - > getPropertySetInfo ( ) - > hasPropertyByName ( PROPERTY_DATASOURCE ) )
_xFormProperties - > getPropertyValue ( PROPERTY_DATASOURCE ) > > = sPropertyValue ;
bHas = ( sPropertyValue . getLength ( ) ! = 0 ) | | _bAllowEmptyDataSourceName ;
// then, the command should not be empty
if ( bHas )
{
if ( _xFormProperties - > getPropertySetInfo ( ) - > hasPropertyByName ( PROPERTY_COMMAND ) )
_xFormProperties - > getPropertyValue ( PROPERTY_COMMAND ) > > = sPropertyValue ;
bHas = ( sPropertyValue . getLength ( ) ! = 0 ) ;
}
}
catch ( const Exception & )
{
OSL_ENSURE ( false , " FormComponentPropertyHandler::impl_hasValidDataSourceSignature_nothrow: caught an exception! " ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
}
return bHas ;
}
//------------------------------------------------------------------------
: : rtl : : OUString FormComponentPropertyHandler : : impl_getDocumentURL_nothrow ( ) const
{
: : rtl : : OUString sURL ;
try
{
Reference < XModel > xDocument ( impl_getContextDocument_nothrow ( ) ) ;
if ( xDocument . is ( ) )
sURL = xDocument - > getURL ( ) ;
}
2008-01-14 13:57:52 +00:00
catch ( const Exception & )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
{
2008-01-14 13:57:52 +00:00
DBG_UNHANDLED_EXCEPTION ( ) ;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
}
return sURL ;
}
2007-07-06 07:48:27 +00:00
// -------------------------------------------------------------------------
: : cppu : : IPropertyArrayHelper * FormComponentPropertyHandler : : createArrayHelper ( ) const
{
uno : : Sequence < beans : : Property > aProps ;
describeProperties ( aProps ) ;
return new : : cppu : : OPropertyArrayHelper ( aProps ) ;
}
// -------------------------------------------------------------------------
: : cppu : : IPropertyArrayHelper & FormComponentPropertyHandler : : getInfoHelper ( )
{
return * const_cast < FormComponentPropertyHandler * > ( this ) - > getArrayHelper ( ) ;
}
// -----------------------------------------------------------------------------
uno : : Reference < beans : : XPropertySetInfo > SAL_CALL FormComponentPropertyHandler : : getPropertySetInfo ( ) throw ( uno : : RuntimeException )
{
return : : cppu : : OPropertySetHelper : : createPropertySetInfo ( getInfoHelper ( ) ) ;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED
2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog
2006/03/08 10:12:20 fs 1.1.2.32: varname typo
2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms
2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers
2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156
2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications
2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications
2005/10/31 13:45:57 fs 1.1.2.26: some cleanup
2005/10/26 14:49:34 fs 1.1.2.25: #i53095#
2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095#
2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup
2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property
2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service)
2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs
2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler
2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking
2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate
2005/10/17 08:17:00 fs 1.1.2.13: #i53095#
2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part
2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model
2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor
2005/09/05 07:41:49 fs 1.1.2.6: #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/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2
moved (nearly) all property handling to dedicated handlers, the controller is
now simply managing a set of handlers
open issues for making the property browser completely generic:
- target page for a property - at the moment, the pbrw uses form-specific
knowledge
- relative position of properties. Again, the pbrw uses the OPropertyInfoService
which is not generic
- isComposeable for a given property. Also OPropertyInfoService-dependent ATM
- help ids of pages and the pbrw as a whole. They're hard-coded at the moment
other open issues:
everything in the code which is tagged with TOD/UNOize. Those are items which
do not immediately hinder phase 3 (real UNOization, i.e. definition of new
UNO interfaces for the handlers, the controller, and so on), but need to be
addressed in phase 4 (knit lose ends)
2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers
2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:44 fs 1.1.2.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:59 fs 1.1.2.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
2006-03-14 10:23:06 +00:00
//........................................................................
} // namespace pcr
//........................................................................