Files
libreoffice/extensions/source/propctrlr/standardcontrol.hxx

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

403 lines
14 KiB
C++
Raw Normal View History

2010-10-27 12:45:03 +01:00
/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
/*
* This file is part of the LibreOffice project.
*
* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/.
*
* This file incorporates work covered by the following license notice:
*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed
* with this work for additional information regarding copyright
* ownership. The ASF licenses this file to you under the Apache
* License, Version 2.0 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of
* the License at http://www.apache.org/licenses/LICENSE-2.0 .
*/
#ifndef INCLUDED_EXTENSIONS_SOURCE_PROPCTRLR_STANDARDCONTROL_HXX
#define INCLUDED_EXTENSIONS_SOURCE_PROPCTRLR_STANDARDCONTROL_HXX
#include "commoncontrol.hxx"
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
#include "pcrcommon.hxx"
#include <com/sun/star/inspection/XNumericControl.hpp>
#include <com/sun/star/inspection/XStringListControl.hpp>
#include <com/sun/star/inspection/XHyperlinkControl.hpp>
#include <com/sun/star/uno/Sequence.hxx>
#include <vcl/field.hxx>
#include <svtools/ctrlbox.hxx>
#include <vcl/lstbox.hxx>
#include <vcl/combobox.hxx>
#include <svtools/calendar.hxx>
#include <vcl/fmtfield.hxx>
#include <svx/colorbox.hxx>
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
#include <set>
class PushButton;
class MultiLineEdit;
namespace pcr
{
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
//= ListLikeControlWithModifyHandler
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
/** Very small helper class which adds a SetModifyHdl to a ListBox-derived class,
thus giving this class the same API (as far as the CommonBehaviourControl is concerned)
as all other windows.
*/
template< class TListboxWindow >
class ListLikeControlWithModifyHandler : public TListboxWindow
{
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
public:
ListLikeControlWithModifyHandler( vcl::Window* _pParent, WinBits _nStyle )
: TListboxWindow( _pParent, _nStyle )
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
{
TListboxWindow::SetSelectHdl( LINK(this, ListLikeControlWithModifyHandler, OnSelect) );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
}
void SetModifyHdl( const Link<TListboxWindow&,void>& _rLink ) { aModifyHdl = _rLink; }
private:
DECL_LINK(OnSelect, TListboxWindow&, void);
Link<TListboxWindow&,void> aModifyHdl;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
};
template< class LISTBOX_WINDOW >
void ListLikeControlWithModifyHandler< LISTBOX_WINDOW >::LinkStubOnSelect(void * instance, LISTBOX_WINDOW& data) {
return static_cast<ListLikeControlWithModifyHandler< LISTBOX_WINDOW > *>(instance)->OnSelect(data);
}
template< class LISTBOX_WINDOW >
void ListLikeControlWithModifyHandler< LISTBOX_WINDOW >::OnSelect(LISTBOX_WINDOW& rListBox)
{
aModifyHdl.Call(rListBox);
}
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
//= OTimeControl
typedef CommonBehaviourControl< css::inspection::XPropertyControl, TimeField > OTimeControl_Base;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
class OTimeControl : public OTimeControl_Base
{
public:
OTimeControl( vcl::Window* pParent, WinBits nWinStyle );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XPropertyControl
virtual css::uno::Any SAL_CALL getValue() override;
virtual void SAL_CALL setValue( const css::uno::Any& _value ) override;
virtual css::uno::Type SAL_CALL getValueType() override;
};
//= ODateControl
typedef CommonBehaviourControl< css::inspection::XPropertyControl, CalendarField > ODateControl_Base;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
class ODateControl : public ODateControl_Base
{
public:
ODateControl( vcl::Window* pParent, WinBits nWinStyle );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XPropertyControl
virtual css::uno::Any SAL_CALL getValue() override;
virtual void SAL_CALL setValue( const css::uno::Any& _value ) override;
virtual css::uno::Type SAL_CALL getValueType() override;
};
//= OEditControl
typedef CommonBehaviourControl< css::inspection::XPropertyControl, Edit > OEditControl_Base;
class OEditControl final : public OEditControl_Base
{
bool m_bIsPassword : 1;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
public:
OEditControl( vcl::Window* _pParent, bool _bPassWord, WinBits nWinStyle );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XPropertyControl
virtual css::uno::Any SAL_CALL getValue() override;
virtual void SAL_CALL setValue( const css::uno::Any& _value ) override;
virtual css::uno::Type SAL_CALL getValueType() override;
private:
// CommonBehaviourControlHelper::modified
virtual void setModified() override;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
};
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
//= ODateTimeControl
typedef CommonBehaviourControl< css::inspection::XPropertyControl, FormattedField > ODateTimeControl_Base;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
class ODateTimeControl : public ODateTimeControl_Base
{
public:
ODateTimeControl( vcl::Window* pParent,WinBits nWinStyle );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XPropertyControl
virtual css::uno::Any SAL_CALL getValue() override;
virtual void SAL_CALL setValue( const css::uno::Any& _value ) override;
virtual css::uno::Type SAL_CALL getValueType() override;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
};
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
//= HyperlinkInput
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
class HyperlinkInput : public Edit
{
private:
Point m_aMouseButtonDownPos;
Link<void*,void> m_aClickHandler;
public:
HyperlinkInput( vcl::Window* _pParent, WinBits _nWinStyle );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
/** sets the handler which will (asynchronously, with locked SolarMutex) be called
when the hyperlink has been clicked by the user
*/
void SetClickHdl( const Link<void*,void>& _rHdl ) { m_aClickHandler = _rHdl; }
protected:
virtual void MouseMove( const MouseEvent& rMEvt ) override;
virtual void MouseButtonDown( const MouseEvent& rMEvt ) override;
virtual void MouseButtonUp( const MouseEvent& rMEvt ) override;
virtual void Tracking( const TrackingEvent& rTEvt ) override;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
private:
void impl_checkEndClick( const MouseEvent& rMEvt );
bool impl_textHitTest( const Point& rWindowPos );
};
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
//= OHyperlinkControl
typedef CommonBehaviourControl< css::inspection::XHyperlinkControl, HyperlinkInput > OHyperlinkControl_Base;
class OHyperlinkControl final : public OHyperlinkControl_Base
{
::comphelper::OInterfaceContainerHelper2 m_aActionListeners;
public:
OHyperlinkControl( vcl::Window* _pParent, WinBits _nWinStyle );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XPropertyControl
virtual css::uno::Any SAL_CALL getValue() override;
virtual void SAL_CALL setValue( const css::uno::Any& _value ) override;
virtual css::uno::Type SAL_CALL getValueType() override;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XHyperlinkControl
virtual void SAL_CALL addActionListener( const css::uno::Reference< css::awt::XActionListener >& listener ) override;
virtual void SAL_CALL removeActionListener( const css::uno::Reference< css::awt::XActionListener >& listener ) override;
private:
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XComponent
virtual void SAL_CALL disposing() override;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
DECL_LINK( OnHyperlinkClicked, void*, void );
};
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
//= CustomConvertibleNumericField
class CustomConvertibleNumericField : public MetricField
{
public:
CustomConvertibleNumericField( vcl::Window* _pParent, WinBits _nStyle )
:MetricField( _pParent, _nStyle )
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
{
}
sal_Int64 GetLastValue() const { return mnLastValue; }
};
//= ONumericControl
typedef CommonBehaviourControl< css::inspection::XNumericControl, CustomConvertibleNumericField > ONumericControl_Base;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
class ONumericControl : public ONumericControl_Base
{
private:
FieldUnit m_eValueUnit;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
sal_Int16 m_nFieldToUNOValueFactor;
public:
ONumericControl( vcl::Window* pParent, WinBits nWinStyle );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XPropertyControl
virtual css::uno::Any SAL_CALL getValue() override;
virtual void SAL_CALL setValue( const css::uno::Any& _value ) override;
virtual css::uno::Type SAL_CALL getValueType() override;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XNumericControl
virtual ::sal_Int16 SAL_CALL getDecimalDigits() override;
virtual void SAL_CALL setDecimalDigits( ::sal_Int16 _decimaldigits ) override;
virtual css::beans::Optional< double > SAL_CALL getMinValue() override;
virtual void SAL_CALL setMinValue( const css::beans::Optional< double >& _minvalue ) override;
virtual css::beans::Optional< double > SAL_CALL getMaxValue() override;
virtual void SAL_CALL setMaxValue( const css::beans::Optional< double >& _maxvalue ) override;
virtual ::sal_Int16 SAL_CALL getDisplayUnit() override;
virtual void SAL_CALL setDisplayUnit( ::sal_Int16 _displayunit ) override;
virtual ::sal_Int16 SAL_CALL getValueUnit() override;
virtual void SAL_CALL setValueUnit( ::sal_Int16 _valueunit ) override;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
private:
/** converts an API value (<code>double</code>, as passed into <code>set[Max|Min|]Value) into
a <code>long</code> value which can be passed to our NumericField.
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
The conversion respects our decimal digits as well as our value factor (<member>m_nFieldToUNOValueFactor</member>).
*/
long impl_apiValueToFieldValue_nothrow( double _nApiValue ) const;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
/** converts a control value, as obtained from our Numeric field, into a value which can passed
to outer callers via our UNO API.
*/
double impl_fieldValueToApiValue_nothrow( sal_Int64 _nFieldValue ) const;
};
//= OColorControl
typedef CommonBehaviourControl < css::inspection::XPropertyControl
, ListLikeControlWithModifyHandler<SvxColorListBox>
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
> OColorControl_Base;
class OColorControl : public OColorControl_Base
{
public:
OColorControl( vcl::Window* pParent, WinBits nWinStyle );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XPropertyControl
virtual css::uno::Any SAL_CALL getValue() override;
virtual void SAL_CALL setValue( const css::uno::Any& _value ) override;
virtual css::uno::Type SAL_CALL getValueType() override;
protected:
// CommonBehaviourControlHelper::setModified
virtual void setModified() override;
};
//= OListboxControl
typedef CommonBehaviourControl < css::inspection::XStringListControl
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
, ListLikeControlWithModifyHandler< ListBox >
> OListboxControl_Base;
class OListboxControl : public OListboxControl_Base
{
public:
OListboxControl( vcl::Window* pParent, WinBits nWinStyle );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XPropertyControl
virtual css::uno::Any SAL_CALL getValue() override;
virtual void SAL_CALL setValue( const css::uno::Any& _value ) override;
virtual css::uno::Type SAL_CALL getValueType() override;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XStringListControl
virtual void SAL_CALL clearList( ) override;
virtual void SAL_CALL prependListEntry( const OUString& NewEntry ) override;
virtual void SAL_CALL appendListEntry( const OUString& NewEntry ) override;
virtual css::uno::Sequence< OUString > SAL_CALL getListEntries( ) override;
protected:
// CommonBehaviourControlHelper::setModified
virtual void setModified() override;
};
//= OComboboxControl
typedef CommonBehaviourControl< css::inspection::XStringListControl, ComboBox > OComboboxControl_Base;
class OComboboxControl final : public OComboboxControl_Base
{
public:
OComboboxControl( vcl::Window* pParent, WinBits nWinStyle );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XPropertyControl
virtual css::uno::Any SAL_CALL getValue() override;
virtual void SAL_CALL setValue( const css::uno::Any& _value ) override;
virtual css::uno::Type SAL_CALL getValueType() override;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XStringListControl
virtual void SAL_CALL clearList( ) override;
virtual void SAL_CALL prependListEntry( const OUString& NewEntry ) override;
virtual void SAL_CALL appendListEntry( const OUString& NewEntry ) override;
virtual css::uno::Sequence< OUString > SAL_CALL getListEntries( ) override;
private:
DECL_LINK( OnEntrySelected, ComboBox&, void );
};
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
//= DropDownEditControl
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
enum MultiLineOperationMode
{
eStringList,
eMultiLineText
};
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
//= DropDownEditControl
class OMultilineFloatingEdit;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
/** an Edit field which can be used as ControlWindow, and has a drop-down button
*/
class DropDownEditControl final : public Edit
{
VclPtr<OMultilineFloatingEdit> m_pFloatingEdit;
VclPtr<MultiLineEdit> m_pImplEdit;
VclPtr<PushButton> m_pDropdownButton;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
MultiLineOperationMode m_nOperationMode;
bool m_bDropdown : 1;
CommonBehaviourControlHelper* m_pHelper;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
public:
DropDownEditControl( vcl::Window* _pParent, WinBits _nStyle );
virtual ~DropDownEditControl() override;
virtual void dispose() override;
void setControlHelper( CommonBehaviourControlHelper& _rControlHelper );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
void setOperationMode( MultiLineOperationMode _eMode ) { m_nOperationMode = _eMode; }
MultiLineOperationMode getOperationMode() const { return m_nOperationMode; }
void SetTextValue( const OUString& _rText );
OUString GetTextValue() const;
void SetStringListValue( const StlSyntaxSequence< OUString >& _rStrings );
StlSyntaxSequence< OUString >
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
GetStringListValue() const;
private:
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// Window overridables
virtual bool PreNotify( NotifyEvent& rNEvt ) override;
virtual void Resize() override;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
long FindPos(long nSinglePos);
DECL_LINK( ReturnHdl, FloatingWindow*, void );
DECL_LINK( DropDownHdl, Button*, void );
void ShowDropDown( bool bShow );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
};
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
//= OMultilineEditControl
typedef CommonBehaviourControl< css::inspection::XPropertyControl, DropDownEditControl > OMultilineEditControl_Base;
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
class OMultilineEditControl : public OMultilineEditControl_Base
{
public:
OMultilineEditControl( vcl::Window* pParent, MultiLineOperationMode _eMode, WinBits nWinStyle );
INTEGRATION: CWS pbrwuno (1.5.158); FILE MERGED 2006/02/10 11:52:35 fs 1.5.158.10: NullPointerException is unusual at addFooListener methods 2005/12/20 10:54:54 fs 1.5.158.9: #i53095# new control type for editing hyperlinks 2005/10/19 07:48:06 fs 1.5.158.8: #i53095# knitting some loose ends 2005/10/17 12:20:19 fs 1.5.158.7: make StringListField exchange a sequence< string > 2005/10/17 10:28:01 fs 1.5.158.6: #i53095# make numeric field exchange its values as double 2005/10/17 07:17:06 fs 1.5.158.5: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:49 fs 1.5.158.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/05 07:10:54 fs 1.5.158.3: RESYNC: (1.5-1.6); FILE MERGED 2005/09/05 07:41:55 fs 1.5.158.2: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/09 14:00:07 fs 1.5.158.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:33:05 +00:00
// XPropertyControl
virtual css::uno::Any SAL_CALL getValue() override;
virtual void SAL_CALL setValue( const css::uno::Any& _value ) override;
virtual css::uno::Type SAL_CALL getValueType() override;
};
} // namespace pcr
#endif // INCLUDED_EXTENSIONS_SOURCE_PROPCTRLR_STANDARDCONTROL_HXX
2010-10-27 12:45:03 +01:00
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */