2010-10-12 15:57:08 +02:00
|
|
|
/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
|
re-base on ALv2 code. Includes (at least) relevant parts of:
linecap: Reintegrating finished LineCap feature
Patch contributed by Regina Henschel
http://svn.apache.org/viewvc?view=revision&revision=1232507
Patches contributed by Sven Jacobi
impress212: #i81610# fixed animation export
http://svn.apache.org/viewvc?view=revision&revision=1167620
impress212: drawinglayer gbuild environment changes
http://svn.apache.org/viewvc?view=revision&revision=1167627
http://svn.apache.org/viewvc?view=revision&revision=1167628
impress212: DffPropSet -> minor code improvements, removing table
http://svn.apache.org/viewvc?view=revision&revision=1167634
impress212: #158494# fixed excel import (text rotation)
http://svn.apache.org/viewvc?view=revision&revision=1167638
Patches contributed by Armin Le Grand
Svg: Reintegrated Svg replacement from /branches/alg/svgreplavement
http://svn.apache.org/viewvc?view=revision&revision=1220836
#118728# changed indentifying definitions for Svg file detection
http://svn.apache.org/viewvc?view=revision&revision=1229961
#118838# LineGeometry creation for complicated cases optimized to
create single Polygons
http://svn.apache.org/viewvc?view=revision&revision=1236232
#119176# corrected file type detection for SVG for svg files
without xml header
http://svn.apache.org/viewvc?view=revision&revision=1309445
#118728# Extended Svg file detection
http://svn.apache.org/viewvc?view=revision&revision=1230531
#118529# solve break converters and convert commands for OLEs and images
http://svn.apache.org/viewvc?view=revision&revision=1186168
svg: added WaE changes from branch svgreplacement to trunc
http://svn.apache.org/viewvc?view=revision&revision=1222974
svg: corrected missing member initialization
http://svn.apache.org/viewvc?view=revision&revision=1226134
fix for #118525#: Using primitives for chart sub-geometry visualisation
http://svn.apache.org/viewvc?view=revision&revision=1226879
#118898# Adapted ImpGraphic::ImplGetBitmap to correctly convert
metafiles to bitmapEx ...
http://svn.apache.org/viewvc?view=revision&revision=1293316
fix for #118525#: removed no longer used variable maOriginalMapMode, one
more exception eliminated
http://svn.apache.org/viewvc?view=revision&revision=1227097
#16758# Added buffering to the VDev usages of the VclProcessor2D derivates...
http://svn.apache.org/viewvc?view=revision&revision=1229521
#116758# Secured VDev buffer device to Vcl deinit
http://svn.apache.org/viewvc?view=revision&revision=1230574
#116758# added remembering allocated VDevs for VDevBuffer to be able to also
delete these when vcl goes down; it should never happen, but You never know
http://svn.apache.org/viewvc?view=revision&revision=1230927
#118730# Changed SvgClipPathNode to use MaskPrimitive2D for primitive
representation instead of TransparencePrimitive2D
http://svn.apache.org/viewvc?view=revision&revision=1231198
#118822# secured 3D geometry creation (slices) by subdividing the 2D
source polyPolygon early
http://svn.apache.org/viewvc?view=revision&revision=1234749
#118829# enhanced Svg gradient quality, obstacles avoided
http://svn.apache.org/viewvc?view=revision&revision=1235361
#118834# Unified usage of TextBreakupHelper as single tooling class
for i18n text primitive breakup
http://svn.apache.org/viewvc?view=revision&revision=1236110
#118853# added square pixel size limit to conversion of
TransparencePrimitive2D to Metafile action
http://svn.apache.org/viewvc?view=revision&revision=1237656
#118824# coreccted mirroring and boundrect when the graphicmanager
is used for bitmap output
http://svn.apache.org/viewvc?view=revision&revision=1240097
#115092# Corrected VclProcessor2D::RenderPolygonStrokePrimitive2D for
various optimization scenarios
http://svn.apache.org/viewvc?view=revision&revision=1241434
#118783# Corrected errors in ID strings, corrected Svg line/fill export,
corrected polygon close state
http://svn.apache.org/viewvc?view=revision&revision=1232006
#118796# corrected null-pointer usage in SVG text exporter
http://svn.apache.org/viewvc?view=revision&revision=1240262
#118729# Use GraphicStreamUrl and GraphicUrl to allow multi image
import with linked graphics, too
http://svn.apache.org/viewvc?view=revision&revision=1229962
#118898# corrected error in GDIMetaFile::GetBoundRect in handling
MetaFloatTransparentAction
http://svn.apache.org/viewvc?view=revision&revision=1293349
#118855# Corrected handling of possibly created empty clipRegions
after PolyPolygon clipping
http://svn.apache.org/viewvc?view=revision&revision=1237725
#115962# Better (but not yet optimal, see comments in task) handling
of MetaFloatTransparentAction in PDF export
http://svn.apache.org/viewvc?view=revision&revision=1241078
IP clearance: #118466# This patch removes librsvg, libcroco, libgsf, ...
http://svn.apache.org/viewvc?view=revision&revision=1200879
118779# Added svg content streaming in/out to ImpGraphic stream operators
http://svn.apache.org/viewvc?view=revision&revision=1231908
linecap: correctons for WaE and mac drawing
http://svn.apache.org/viewvc?view=revision&revision=1232793
svg: uses current system Dpi for Svg replacement image creation
http://svn.apache.org/viewvc?view=revision&revision=1233948
Patches contributed by Mathias Bauer (and others)
gnumake4 work variously
http://svn.apache.org/viewvc?view=revision&revision=1394326
http://svn.apache.org/viewvc?view=revision&revision=1396797
http://svn.apache.org/viewvc?view=revision&revision=1397315
http://svn.apache.org/viewvc?view=revision&revision=1394326
Remove duplicate header includes.
cws mba34issues01: #i117720#: convert assertion into warning
http://svn.apache.org/viewvc?view=revision&revision=1172352
118485 - Styles for OLEs are not saved. Submitted by Armin Le Grand.
http://svn.apache.org/viewvc?view=revision&revision=1182166
cws mba34issues01: #i117714#: remove assertion
http://svn.apache.org/viewvc?view=revision&revision=1172357
Patch contributed by Jurgen Schmidt
add some additional checks to ensure proper reading operations
http://svn.apache.org/viewvc?view=revision&revision=1209022
mostly prefer our stream / bounds checking work.
Patches contributed by Herbert Duerr
#i118816# add clarifying comment regarding Font::*Color*() methods
http://svn.apache.org/viewvc?view=revision&revision=1233833
extend macro->string handling for empty strings
http://svn.apache.org/viewvc?view=revision&revision=1175801
avoid magic constants for SALCOLOR_NONE
http://svn.apache.org/viewvc?view=revision&revision=1177543
initialize slant properly in ImplFontMetricData constructor (author=iorsh)
http://svn.apache.org/viewvc?view=revision&revision=1177551
#i118675# make check for extension updates more stable
http://svn.apache.org/viewvc?view=revision&revision=1214797
#a118617# remove VBasicEventListener.dll binary
There are no known users depending on its CLSID
http://svn.apache.org/viewvc?view=revision&revision=1203697
Patches contributed by Ariel Constenla-Haile
Fix build breaker on Linux/gcc
http://svn.apache.org/viewvc?view=revision&revision=1221104
Fix crash when trying to instantiate css.graphic.GraphicRasterizer_RSVG
http://svn.apache.org/viewvc?view=revision&revision=1215559
Patches contributed by Oliver-Rainer Wittmann
sw34bf06: #i117962# - method <SwFlyFrm::IsPaint(..)> - consider
instances of <SwFlyDrawObj>
http://svn.apache.org/viewvc?view=revision&revision=1172120
sw34bf06: #i117783# - Writer's implementation of XPagePrintable -
apply print settings to new printing routines
http://svn.apache.org/viewvc?view=revision&revision=1172115
gnumake4 work variously from Hans-Joachim Lankenau
http://svn.apache.org/viewvc?view=revision&revision=1397315
http://svn.apache.org/viewvc?view=revision&revision=1396797
http://svn.apache.org/viewvc?view=revision&revision=1396782
http://svn.apache.org/viewvc?view=revision&revision=1394707
plus some amount of re-splitting of legacy headers.
Patch contributed by Pavel Janik
WaE: Remove unused variables.
http://svn.apache.org/viewvc?view=revision&revision=1230697
Patches contributed by Takashi Ono
mingwport35: i#117795: MinGW port fix for vcl2gnumake
http://svn.apache.org/viewvc?view=revision&revision=1172091
mingwport35: i#117795: MinGW port fix for vcl2gnumake
http://svn.apache.org/viewvc?view=revision&revision=1172091
Patch contributed by Christian Lippka
impress212: #i98044# re enable Text menu for outline and title shapes
http://svn.apache.org/viewvc?view=revision&revision=1167639
Patch contributed by Andre Fischer
118674: Made category B code optional and disabled by default.
http://svn.apache.org/viewvc?view=revision&revision=1215131
118881: Ignore empty paragraphs after bullets.
http://svn.apache.org/viewvc?view=revision&revision=1296205
Patches contributed by Philipp Lohmann
ooo340fixes: #i117780# use rtl allocator
http://svn.apache.org/viewvc?view=revision&revision=1172087
ooo34gsl02: #i117807# fix an off by one error (index actually
inside the pfb section header)
http://svn.apache.org/viewvc?view=revision&revision=1167576
various cleanups, related compilation fixes, warning cleanups, re-working
of obsolete stl template pieces to use boost instead, changed string
classes, re-adapt KDE about data, about dialog, fixing warnings,
and other fixes & improvements.
Disable svg import / render for about/ branding code-paths for now.
Restore full icon theme set.
Remove OS/2 conditionals and sources.
Remove conflicting gtk/full-screen monitors support.
Retain existing svg rasterizer files - temporarily disabled.
Standardize stringificaiton and fixup dllpostfix issues.
Rename SvgGradientHelper::== to equalTo to avoid overloading issues.
Use the flat GdiPlus API for LineCaps calls.
2012-10-09 12:22:23 +01:00
|
|
|
/*
|
|
|
|
* 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 .
|
|
|
|
*/
|
2001-01-12 10:35:45 +00:00
|
|
|
|
|
|
|
#include "standardcontrol.hxx"
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
#include "pcrcommon.hxx"
|
2004-11-16 11:12:31 +00:00
|
|
|
|
2017-02-06 17:08:38 +01:00
|
|
|
#include <com/sun/star/beans/IllegalTypeException.hpp>
|
2004-11-16 11:12:31 +00:00
|
|
|
#include <com/sun/star/util/DateTime.hpp>
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
#include <com/sun/star/util/Date.hpp>
|
|
|
|
#include <com/sun/star/util/Time.hpp>
|
|
|
|
#include <com/sun/star/util/Color.hpp>
|
|
|
|
#include <com/sun/star/util/MeasureUnit.hpp>
|
|
|
|
#include <com/sun/star/inspection/PropertyControlType.hpp>
|
2012-01-02 10:55:27 +00:00
|
|
|
#include <comphelper/string.hxx>
|
2019-08-13 10:54:44 +02:00
|
|
|
#include <o3tl/float_int_conversion.hxx>
|
2003-03-25 15:04:55 +00:00
|
|
|
#include <rtl/math.hxx>
|
2001-01-12 10:35:45 +00:00
|
|
|
#include <sfx2/objsh.hxx>
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
// ugly dependencies for the OColorControl
|
|
|
|
#include <svx/svxids.hrc>
|
|
|
|
#include <svx/drawitem.hxx>
|
2010-04-24 00:08:18 +02:00
|
|
|
#include <svx/xtable.hxx>
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
#include <vcl/floatwin.hxx>
|
|
|
|
#include <svtools/svmedit.hxx>
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
#include <svtools/colorcfg.hxx>
|
2018-11-19 01:06:09 +01:00
|
|
|
#include <svl/zforlist.hxx>
|
2009-10-16 00:05:16 +02:00
|
|
|
#include <unotools/syslocale.hxx>
|
2004-11-16 11:12:31 +00:00
|
|
|
#include <unotools/datetime.hxx>
|
2013-04-05 18:40:39 +02:00
|
|
|
#include <i18nlangtag/languagetag.hxx>
|
2001-01-12 10:35:45 +00:00
|
|
|
#include <vcl/button.hxx>
|
2019-01-30 00:10:38 +01:00
|
|
|
#include <vcl/event.hxx>
|
2001-01-12 10:35:45 +00:00
|
|
|
#include <vcl/svapp.hxx>
|
2014-01-02 23:52:37 +01:00
|
|
|
#include <vcl/settings.hxx>
|
2019-02-12 10:12:03 +02:00
|
|
|
#include <vcl/ptrstyle.hxx>
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-03-03 18:27:00 +01:00
|
|
|
#include <cstdlib>
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
#include <limits>
|
2015-09-18 11:51:16 +01:00
|
|
|
#include <memory>
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
namespace pcr
|
|
|
|
{
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2004-11-16 11:12:31 +00:00
|
|
|
using namespace ::com::sun::star;
|
|
|
|
using namespace ::com::sun::star::uno;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
using namespace ::com::sun::star::awt;
|
2004-11-16 11:12:31 +00:00
|
|
|
using namespace ::com::sun::star::lang;
|
|
|
|
using namespace ::com::sun::star::util;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
using namespace ::com::sun::star::beans;
|
|
|
|
using namespace ::com::sun::star::inspection;
|
2004-11-16 11:12:31 +00:00
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
//= OTimeControl
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
OTimeControl::OTimeControl( vcl::Window* pParent, WinBits nWinStyle )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
:OTimeControl_Base( PropertyControlType::TimeField, pParent, nWinStyle )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-02-21 12:53:51 +01:00
|
|
|
getTypedControlWindow()->SetStrictFormat( true );
|
2014-10-27 20:41:11 +02:00
|
|
|
getTypedControlWindow()->SetFormat( TimeFieldFormat::F_SEC );
|
2014-02-21 12:53:51 +01:00
|
|
|
getTypedControlWindow()->EnableEmptyFieldValue( true );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OTimeControl::setValue( const Any& _rValue )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
util::Time aUNOTime;
|
|
|
|
if ( !( _rValue >>= aUNOTime ) )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2013-09-19 15:20:39 +02:00
|
|
|
getTypedControlWindow()->SetText( "" );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->SetEmptyTime();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
2015-01-11 13:35:38 +02:00
|
|
|
getTypedControlWindow()->SetTime( ::tools::Time(aUNOTime) );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Any SAL_CALL OTimeControl::getValue()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
Any aPropValue;
|
2013-01-21 14:32:09 +01:00
|
|
|
if ( !getTypedControlWindow()->GetText().isEmpty() )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2013-08-04 01:14:22 +02:00
|
|
|
aPropValue <<= getTypedControlWindow()->GetTime().GetUNOTime();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
return aPropValue;
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Type SAL_CALL OTimeControl::getValueType()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-05-14 23:17:17 +02:00
|
|
|
return ::cppu::UnoType<util::Time>::get();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
//= ODateControl
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
ODateControl::ODateControl( vcl::Window* pParent, WinBits nWinStyle )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
:ODateControl_Base( PropertyControlType::DateField, pParent, nWinStyle | WB_DROPDOWN )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2015-10-09 17:40:07 +02:00
|
|
|
CalendarField* pControlWindow = getTypedControlWindow();
|
2014-02-21 12:53:51 +01:00
|
|
|
pControlWindow->SetStrictFormat(true);
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
pControlWindow->SetMin( ::Date( 1,1,1600 ) );
|
|
|
|
pControlWindow->SetFirst( ::Date( 1,1,1600 ) );
|
|
|
|
pControlWindow->SetLast( ::Date( 1, 1, 9999 ) );
|
|
|
|
pControlWindow->SetMax( ::Date( 1, 1, 9999 ) );
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2016-09-02 11:55:30 +02:00
|
|
|
pControlWindow->SetExtDateFormat( ExtDateFieldFormat::SystemShortYYYY );
|
2014-02-21 12:53:51 +01:00
|
|
|
pControlWindow->EnableEmptyFieldValue( true );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL ODateControl::setValue( const Any& _rValue )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
util::Date aUNODate;
|
|
|
|
if ( !( _rValue >>= aUNODate ) )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2013-09-19 15:20:39 +02:00
|
|
|
getTypedControlWindow()->SetText( "" );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->SetEmptyDate();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
::Date aDate( aUNODate.Day, aUNODate.Month, aUNODate.Year );
|
|
|
|
getTypedControlWindow()->SetDate( aDate );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Any SAL_CALL ODateControl::getValue()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
Any aPropValue;
|
2013-01-21 14:32:09 +01:00
|
|
|
if ( !getTypedControlWindow()->GetText().isEmpty() )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
::Date aDate( getTypedControlWindow()->GetDate() );
|
2015-01-11 13:35:38 +02:00
|
|
|
aPropValue <<= aDate.GetUNODate();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
return aPropValue;
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Type SAL_CALL ODateControl::getValueType()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-05-14 23:17:17 +02:00
|
|
|
return ::cppu::UnoType<util::Date>::get();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
//= OEditControl
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
OEditControl::OEditControl(vcl::Window* _pParent, bool _bPW, WinBits _nWinStyle)
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
:OEditControl_Base( _bPW ? PropertyControlType::CharacterField : PropertyControlType::TextField, _pParent, _nWinStyle )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
|
|
|
m_bIsPassword = _bPW;
|
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( m_bIsPassword )
|
|
|
|
getTypedControlWindow()->SetMaxTextLen( 1 );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OEditControl::setValue( const Any& _rValue )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2013-04-07 12:06:47 +02:00
|
|
|
OUString sText;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( m_bIsPassword )
|
|
|
|
{
|
|
|
|
sal_Int16 nValue = 0;
|
|
|
|
_rValue >>= nValue;
|
|
|
|
if ( nValue )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2013-04-07 12:06:47 +02:00
|
|
|
sText = OUString(static_cast<sal_Unicode>(nValue));
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
else
|
|
|
|
_rValue >>= sText;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->SetText( sText );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Any SAL_CALL OEditControl::getValue()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
Any aPropValue;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2013-04-07 12:06:47 +02:00
|
|
|
OUString sText( getTypedControlWindow()->GetText() );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( m_bIsPassword )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2011-12-22 15:35:41 -02:00
|
|
|
if ( !sText.isEmpty() )
|
2018-01-12 20:24:28 +01:00
|
|
|
aPropValue <<= static_cast<sal_Int16>(sText[0]);
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
else
|
|
|
|
aPropValue <<= sText;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
return aPropValue;
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Type SAL_CALL OEditControl::getValueType()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-05-11 10:09:04 +02:00
|
|
|
return m_bIsPassword ? ::cppu::UnoType<sal_Int16>::get() : ::cppu::UnoType<OUString>::get();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2015-10-09 17:44:20 +02:00
|
|
|
void OEditControl::setModified()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2015-10-09 17:44:20 +02:00
|
|
|
OEditControl_Base::setModified();
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-02-06 21:49:21 +01:00
|
|
|
// for password controls, we fire a commit for every single change
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( m_bIsPassword )
|
2015-10-09 15:17:24 +02:00
|
|
|
notifyModifiedValue();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
static long ImplCalcLongValue( double nValue, sal_uInt16 nDigits )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
|
|
|
double n = nValue;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
for ( sal_uInt16 d = 0; d < nDigits; ++d )
|
2001-01-12 10:35:45 +00:00
|
|
|
n *= 10;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
|
2019-08-13 10:54:44 +02:00
|
|
|
if ( !o3tl::convertsToAtMost(n, std::numeric_limits< long >::max()) )
|
2017-02-17 19:06:24 +02:00
|
|
|
return std::numeric_limits< long >::max();
|
2018-01-12 20:24:28 +01:00
|
|
|
return static_cast<long>(n);
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
static double ImplCalcDoubleValue( long nValue, sal_uInt16 nDigits )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
|
|
|
double n = nValue;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
for ( sal_uInt16 d = 0; d < nDigits; ++d )
|
2001-01-12 10:35:45 +00:00
|
|
|
n /= 10;
|
|
|
|
return n;
|
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2004-11-16 11:12:31 +00:00
|
|
|
// class ODateTimeControl
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
ODateTimeControl::ODateTimeControl( vcl::Window* _pParent, WinBits _nWinStyle)
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
:ODateTimeControl_Base( PropertyControlType::DateTimeField, _pParent, _nWinStyle )
|
2004-11-16 11:12:31 +00:00
|
|
|
{
|
2014-03-20 11:53:43 +02:00
|
|
|
getTypedControlWindow()->EnableEmptyField( true );
|
2004-11-16 11:12:31 +00:00
|
|
|
|
|
|
|
// determine a default format
|
2012-11-23 23:06:10 +01:00
|
|
|
LanguageType eSysLanguage = SvtSysLocale().GetLanguageTag().getLanguageType( false);
|
2004-11-16 11:12:31 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->SetFormatter( getTypedControlWindow()->StandardFormatter() );
|
|
|
|
SvNumberFormatter* pFormatter = getTypedControlWindow()->GetFormatter();
|
2017-12-03 21:46:37 +02:00
|
|
|
sal_uLong nStandardDateTimeFormat = pFormatter->GetStandardFormat( SvNumFormatType::DATETIME, eSysLanguage );
|
2004-11-16 11:12:31 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->SetFormatKey( nStandardDateTimeFormat );
|
2004-11-16 11:12:31 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL ODateTimeControl::setValue( const Any& _rValue )
|
2004-11-16 11:12:31 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( !_rValue.hasValue() )
|
2004-11-16 11:12:31 +00:00
|
|
|
{
|
2013-09-19 15:20:39 +02:00
|
|
|
getTypedControlWindow()->SetText( "" );
|
2004-11-16 11:12:31 +00:00
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
util::DateTime aUNODateTime;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
OSL_VERIFY( _rValue >>= aUNODateTime );
|
2004-11-16 11:12:31 +00:00
|
|
|
|
2011-12-01 21:03:42 +01:00
|
|
|
::DateTime aDateTime( ::DateTime::EMPTY );
|
2004-11-16 11:12:31 +00:00
|
|
|
::utl::typeConvert( aUNODateTime, aDateTime );
|
|
|
|
|
2017-07-18 19:43:05 +02:00
|
|
|
double nValue = aDateTime - ::DateTime( getTypedControlWindow()->GetFormatter()->GetNullDate() );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->SetValue( nValue );
|
2004-11-16 11:12:31 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Any SAL_CALL ODateTimeControl::getValue()
|
2004-11-16 11:12:31 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
Any aPropValue;
|
2013-01-21 14:32:09 +01:00
|
|
|
if ( !getTypedControlWindow()->GetText().isEmpty() )
|
2004-11-16 11:12:31 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
double nValue = getTypedControlWindow()->GetValue();
|
2004-11-16 11:12:31 +00:00
|
|
|
|
2017-07-18 19:43:05 +02:00
|
|
|
::DateTime aDateTime( getTypedControlWindow()->GetFormatter()->GetNullDate() );
|
2004-11-16 11:12:31 +00:00
|
|
|
|
|
|
|
// add the "days" part
|
|
|
|
double nDays = floor( nValue );
|
2017-07-21 13:32:10 +02:00
|
|
|
aDateTime.AddDays( nDays );
|
2004-11-16 11:12:31 +00:00
|
|
|
|
|
|
|
// add the "time" part
|
|
|
|
double nTime = nValue - nDays;
|
|
|
|
nTime = ::rtl::math::round( nTime * 86400.0 ) / 86400.0;
|
|
|
|
// we're not interested in 100th seconds, and this here prevents rounding errors
|
2017-07-21 13:32:10 +02:00
|
|
|
aDateTime.AddTime( nTime );
|
2004-11-16 11:12:31 +00:00
|
|
|
|
|
|
|
util::DateTime aUNODateTime;
|
|
|
|
::utl::typeConvert( aDateTime, aUNODateTime );
|
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
aPropValue <<= aUNODateTime;
|
|
|
|
}
|
|
|
|
return aPropValue;
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Type SAL_CALL ODateTimeControl::getValueType()
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2014-05-14 23:17:17 +02:00
|
|
|
return ::cppu::UnoType<util::DateTime>::get();
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
//= HyperlinkInput
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
HyperlinkInput::HyperlinkInput( vcl::Window* _pParent, WinBits _nWinStyle )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
:Edit( _pParent, _nWinStyle )
|
|
|
|
{
|
|
|
|
::svtools::ColorConfig aColorConfig;
|
|
|
|
::svtools::ColorConfigValue aLinkColor( aColorConfig.GetColorValue( ::svtools::LINKS ) );
|
|
|
|
|
|
|
|
AllSettings aAllSettings( GetSettings() );
|
|
|
|
StyleSettings aStyleSettings( aAllSettings.GetStyleSettings() );
|
|
|
|
|
2014-09-16 10:09:58 +02:00
|
|
|
vcl::Font aFieldFont( aStyleSettings.GetFieldFont() );
|
2016-01-29 17:43:42 +11:00
|
|
|
aFieldFont.SetUnderline( LINESTYLE_SINGLE );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
aFieldFont.SetColor( aLinkColor.nColor );
|
|
|
|
aStyleSettings.SetFieldFont( aFieldFont );
|
|
|
|
|
|
|
|
aStyleSettings.SetFieldTextColor( aLinkColor.nColor );
|
|
|
|
|
|
|
|
aAllSettings.SetStyleSettings( aStyleSettings );
|
|
|
|
SetSettings( aAllSettings );
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
void HyperlinkInput::MouseMove( const ::MouseEvent& rMEvt )
|
|
|
|
{
|
|
|
|
Edit::MouseMove( rMEvt );
|
|
|
|
|
2015-05-20 14:05:50 +02:00
|
|
|
PointerStyle ePointerStyle( PointerStyle::Text );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
|
|
|
|
if ( !rMEvt.IsLeaveWindow() )
|
|
|
|
{
|
|
|
|
if ( impl_textHitTest( rMEvt.GetPosPixel() ) )
|
2015-05-20 14:05:50 +02:00
|
|
|
ePointerStyle = PointerStyle::RefHand;
|
2004-11-16 11:12:31 +00:00
|
|
|
}
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
|
2019-02-12 10:12:03 +02:00
|
|
|
SetPointer( ePointerStyle );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
void HyperlinkInput::MouseButtonDown( const ::MouseEvent& rMEvt )
|
|
|
|
{
|
|
|
|
Edit::MouseButtonDown( rMEvt );
|
|
|
|
|
|
|
|
if ( impl_textHitTest( rMEvt.GetPosPixel() ) )
|
|
|
|
m_aMouseButtonDownPos = rMEvt.GetPosPixel();
|
|
|
|
else
|
2018-02-27 17:10:36 +02:00
|
|
|
{
|
|
|
|
m_aMouseButtonDownPos.setX(-1);
|
|
|
|
m_aMouseButtonDownPos.setY(-1);
|
|
|
|
}
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
void HyperlinkInput::MouseButtonUp( const ::MouseEvent& rMEvt )
|
|
|
|
{
|
|
|
|
Edit::MouseButtonUp( rMEvt );
|
|
|
|
|
|
|
|
impl_checkEndClick( rMEvt );
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2008-06-25 13:53:11 +00:00
|
|
|
bool HyperlinkInput::impl_textHitTest( const ::Point& _rWindowPos )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2013-11-29 11:45:09 +02:00
|
|
|
sal_Int32 nPos = GetCharPos( _rWindowPos );
|
2014-01-13 18:36:07 +00:00
|
|
|
return ( ( nPos != EDIT_NOLIMIT ) && ( nPos < GetText().getLength() ) );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2015-03-09 10:11:00 +00:00
|
|
|
void HyperlinkInput::impl_checkEndClick( const ::MouseEvent& rMEvt )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
const MouseSettings& rMouseSettings( GetSettings().GetMouseSettings() );
|
2014-03-03 18:27:00 +01:00
|
|
|
if ( ( std::abs( rMEvt.GetPosPixel().X() - m_aMouseButtonDownPos.X() ) < rMouseSettings.GetStartDragWidth() )
|
|
|
|
&& ( std::abs( rMEvt.GetPosPixel().Y() - m_aMouseButtonDownPos.Y() ) < rMouseSettings.GetStartDragHeight() )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
)
|
|
|
|
Application::PostUserEvent( m_aClickHandler );
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
void HyperlinkInput::Tracking( const TrackingEvent& rTEvt )
|
|
|
|
{
|
|
|
|
Edit::Tracking( rTEvt );
|
|
|
|
|
|
|
|
if ( rTEvt.IsTrackingEnded() )
|
|
|
|
impl_checkEndClick( rTEvt.GetMouseEvent() );
|
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
//= OHyperlinkControl
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
OHyperlinkControl::OHyperlinkControl( vcl::Window* _pParent, WinBits _nWinStyle )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
:OHyperlinkControl_Base( PropertyControlType::HyperlinkField, _pParent, _nWinStyle )
|
|
|
|
,m_aActionListeners( m_aMutex )
|
|
|
|
{
|
|
|
|
getTypedControlWindow()->SetClickHdl( LINK( this, OHyperlinkControl, OnHyperlinkClicked ) );
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Any SAL_CALL OHyperlinkControl::getValue()
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2013-04-07 12:06:47 +02:00
|
|
|
OUString sText = getTypedControlWindow()->GetText();
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
return makeAny( sText );
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OHyperlinkControl::setValue( const Any& _value )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2013-04-07 12:06:47 +02:00
|
|
|
OUString sText;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
_value >>= sText;
|
|
|
|
getTypedControlWindow()->SetText( sText );
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Type SAL_CALL OHyperlinkControl::getValueType()
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2014-05-11 10:09:04 +02:00
|
|
|
return ::cppu::UnoType<OUString>::get();
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OHyperlinkControl::addActionListener( const Reference< XActionListener >& listener )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
if ( listener.is() )
|
|
|
|
m_aActionListeners.addInterface( listener );
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OHyperlinkControl::removeActionListener( const Reference< XActionListener >& listener )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
m_aActionListeners.removeInterface( listener );
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
void SAL_CALL OHyperlinkControl::disposing()
|
|
|
|
{
|
|
|
|
OHyperlinkControl_Base::disposing();
|
|
|
|
|
|
|
|
EventObject aEvent( *this );
|
|
|
|
m_aActionListeners.disposeAndClear( aEvent );
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2016-10-05 07:56:12 +02:00
|
|
|
IMPL_LINK_NOARG( OHyperlinkControl, OnHyperlinkClicked, void*, void )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2017-01-30 16:38:54 +02:00
|
|
|
ActionEvent aEvent( *this, "clicked" );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
m_aActionListeners.forEach< XActionListener >(
|
2017-01-14 19:58:35 +01:00
|
|
|
[&aEvent] (uno::Reference<awt::XActionListener> const& xListener)
|
2016-02-02 15:47:41 +01:00
|
|
|
{ return xListener->actionPerformed(aEvent); });
|
2004-11-16 11:12:31 +00:00
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
//= ONumericControl
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
ONumericControl::ONumericControl( vcl::Window* _pParent, WinBits _nWinStyle )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
:ONumericControl_Base( PropertyControlType::NumericField, _pParent, _nWinStyle )
|
2018-11-06 14:37:23 +03:00
|
|
|
,m_eValueUnit( FieldUnit::NONE )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
,m_nFieldToUNOValueFactor( 1 )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2018-11-06 14:37:23 +03:00
|
|
|
MetricField::SetDefaultUnit( FieldUnit::NONE );
|
2004-03-19 11:06:39 +00:00
|
|
|
|
2014-02-21 12:53:51 +01:00
|
|
|
getTypedControlWindow()->EnableEmptyFieldValue( true );
|
|
|
|
getTypedControlWindow()->SetStrictFormat( true );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
Optional< double > value( getMaxValue() );
|
|
|
|
value.Value = -value.Value;
|
|
|
|
setMinValue( value );
|
|
|
|
}
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
::sal_Int16 SAL_CALL ONumericControl::getDecimalDigits()
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
return getTypedControlWindow()->GetDecimalDigits();
|
|
|
|
}
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL ONumericControl::setDecimalDigits( ::sal_Int16 _decimaldigits )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
getTypedControlWindow()->SetDecimalDigits( _decimaldigits );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Optional< double > SAL_CALL ONumericControl::getMinValue()
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2016-04-20 17:16:53 +02:00
|
|
|
Optional< double > aReturn( true, 0 );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
|
2007-05-10 09:50:15 +00:00
|
|
|
sal_Int64 minValue = getTypedControlWindow()->GetMin();
|
2017-02-17 19:06:24 +02:00
|
|
|
if ( minValue == std::numeric_limits< sal_Int64 >::min() )
|
2016-04-20 17:16:53 +02:00
|
|
|
aReturn.IsPresent = false;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
else
|
2018-01-12 20:24:28 +01:00
|
|
|
aReturn.Value = static_cast<double>(minValue);
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
|
|
|
|
return aReturn;
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL ONumericControl::setMinValue( const Optional< double >& _minvalue )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
if ( !_minvalue.IsPresent )
|
2017-02-17 19:06:24 +02:00
|
|
|
getTypedControlWindow()->SetMin( std::numeric_limits< sal_Int64 >::min() );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
else
|
2007-11-20 18:52:38 +00:00
|
|
|
getTypedControlWindow()->SetMin( impl_apiValueToFieldValue_nothrow( _minvalue.Value ) , m_eValueUnit);
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Optional< double > SAL_CALL ONumericControl::getMaxValue()
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2016-04-20 17:16:53 +02:00
|
|
|
Optional< double > aReturn( true, 0 );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
|
2007-05-10 09:50:15 +00:00
|
|
|
sal_Int64 maxValue = getTypedControlWindow()->GetMax();
|
2017-02-17 19:06:24 +02:00
|
|
|
if ( maxValue == std::numeric_limits< sal_Int64 >::max() )
|
2016-04-20 17:16:53 +02:00
|
|
|
aReturn.IsPresent = false;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
else
|
2018-01-12 20:24:28 +01:00
|
|
|
aReturn.Value = static_cast<double>(maxValue);
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
|
|
|
|
return aReturn;
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL ONumericControl::setMaxValue( const Optional< double >& _maxvalue )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
if ( !_maxvalue.IsPresent )
|
2017-02-17 19:06:24 +02:00
|
|
|
getTypedControlWindow()->SetMax( std::numeric_limits< sal_Int64 >::max() );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
else
|
2007-11-20 18:52:38 +00:00
|
|
|
getTypedControlWindow()->SetMax( impl_apiValueToFieldValue_nothrow( _maxvalue.Value ), m_eValueUnit );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
::sal_Int16 SAL_CALL ONumericControl::getDisplayUnit()
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2007-07-06 07:54:12 +00:00
|
|
|
return VCLUnoHelper::ConvertToMeasurementUnit( getTypedControlWindow()->GetUnit(), 1 );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL ONumericControl::setDisplayUnit( ::sal_Int16 _displayunit )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
if ( ( _displayunit < MeasureUnit::MM_100TH ) || ( _displayunit > MeasureUnit::PERCENT ) )
|
|
|
|
throw IllegalArgumentException();
|
|
|
|
if ( ( _displayunit == MeasureUnit::MM_100TH )
|
|
|
|
|| ( _displayunit == MeasureUnit::MM_10TH )
|
|
|
|
|| ( _displayunit == MeasureUnit::INCH_1000TH )
|
|
|
|
|| ( _displayunit == MeasureUnit::INCH_100TH )
|
|
|
|
|| ( _displayunit == MeasureUnit::INCH_10TH )
|
|
|
|
|| ( _displayunit == MeasureUnit::PERCENT )
|
|
|
|
)
|
|
|
|
throw IllegalArgumentException();
|
|
|
|
|
|
|
|
sal_Int16 nDummyFactor = 1;
|
2007-07-06 07:54:12 +00:00
|
|
|
FieldUnit eFieldUnit = VCLUnoHelper::ConvertToFieldUnit( _displayunit, nDummyFactor );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( nDummyFactor != 1 )
|
|
|
|
// everything which survived the checks above should result in a factor of 1, i.e.,
|
|
|
|
// it should have a direct counterpart as FieldUnit
|
|
|
|
throw RuntimeException();
|
2010-11-23 21:38:52 +01:00
|
|
|
getTypedControlWindow()->MetricFormatter::SetUnit( eFieldUnit );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
::sal_Int16 SAL_CALL ONumericControl::getValueUnit()
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2007-07-06 07:54:12 +00:00
|
|
|
return VCLUnoHelper::ConvertToMeasurementUnit( m_eValueUnit, m_nFieldToUNOValueFactor );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL ONumericControl::setValueUnit( ::sal_Int16 _valueunit )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
if ( ( _valueunit < MeasureUnit::MM_100TH ) || ( _valueunit > MeasureUnit::PERCENT ) )
|
|
|
|
throw IllegalArgumentException();
|
2007-07-06 07:54:12 +00:00
|
|
|
m_eValueUnit = VCLUnoHelper::ConvertToFieldUnit( _valueunit, m_nFieldToUNOValueFactor );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL ONumericControl::setValue( const Any& _rValue )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( !_rValue.hasValue() )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2013-09-19 15:20:39 +02:00
|
|
|
getTypedControlWindow()->SetText( "" );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->SetEmptyFieldValue();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
double nValue( 0 );
|
|
|
|
OSL_VERIFY( _rValue >>= nValue );
|
|
|
|
long nControlValue = impl_apiValueToFieldValue_nothrow( nValue );
|
|
|
|
getTypedControlWindow()->SetValue( nControlValue, m_eValueUnit );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
long ONumericControl::impl_apiValueToFieldValue_nothrow( double _nApiValue ) const
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
long nControlValue = ImplCalcLongValue( _nApiValue, getTypedControlWindow()->GetDecimalDigits() );
|
|
|
|
nControlValue /= m_nFieldToUNOValueFactor;
|
|
|
|
return nControlValue;
|
|
|
|
}
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2007-05-10 09:50:15 +00:00
|
|
|
double ONumericControl::impl_fieldValueToApiValue_nothrow( sal_Int64 _nFieldValue ) const
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2018-01-12 20:24:28 +01:00
|
|
|
double nApiValue = ImplCalcDoubleValue( static_cast<long>(_nFieldValue), getTypedControlWindow()->GetDecimalDigits() );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
nApiValue *= m_nFieldToUNOValueFactor;
|
|
|
|
return nApiValue;
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Any SAL_CALL ONumericControl::getValue()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
Any aPropValue;
|
2013-01-21 14:32:09 +01:00
|
|
|
if ( !getTypedControlWindow()->GetText().isEmpty() )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
double nValue = impl_fieldValueToApiValue_nothrow( getTypedControlWindow()->GetValue( m_eValueUnit ) );
|
|
|
|
aPropValue <<= nValue;
|
|
|
|
}
|
|
|
|
return aPropValue;
|
|
|
|
}
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Type SAL_CALL ONumericControl::getValueType()
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2014-05-11 10:09:04 +02:00
|
|
|
return ::cppu::UnoType<double>::get();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
//= OColorControl
|
2014-02-25 18:36:00 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
#define LB_DEFAULT_COUNT 20
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
OColorControl::OColorControl(vcl::Window* pParent, WinBits nWinStyle)
|
2016-11-05 20:28:27 +00:00
|
|
|
: OColorControl_Base(PropertyControlType::ColorListBox, pParent, nWinStyle)
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2017-05-22 12:05:17 +01:00
|
|
|
getTypedControlWindow()->SetSlotId(SID_FM_CTL_PROPERTIES);
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OColorControl::setValue( const Any& _rValue )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2018-02-26 17:13:01 +02:00
|
|
|
css::util::Color nColor = sal_uInt32(COL_TRANSPARENT);
|
2017-05-22 12:05:17 +01:00
|
|
|
if (_rValue.hasValue())
|
2016-11-05 20:28:27 +00:00
|
|
|
_rValue >>= nColor;
|
2018-03-07 08:42:58 +02:00
|
|
|
getTypedControlWindow()->SelectEntry(nColor);
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Any SAL_CALL OColorControl::getValue()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
Any aPropValue;
|
2017-05-22 12:05:17 +01:00
|
|
|
::Color aRgbCol = getTypedControlWindow()->GetSelectEntryColor();
|
|
|
|
if (aRgbCol == COL_TRANSPARENT)
|
|
|
|
return aPropValue;
|
2018-03-07 08:42:58 +02:00
|
|
|
aPropValue <<= aRgbCol;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
return aPropValue;
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Type SAL_CALL OColorControl::getValueType()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-05-11 10:09:04 +02:00
|
|
|
return ::cppu::UnoType<sal_Int32>::get();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2015-10-09 17:44:20 +02:00
|
|
|
void OColorControl::setModified()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2015-10-09 17:44:20 +02:00
|
|
|
OColorControl_Base::setModified();
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2016-11-05 20:28:27 +00:00
|
|
|
// fire a commit
|
|
|
|
notifyModifiedValue();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
//= OListboxControl
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
OListboxControl::OListboxControl( vcl::Window* pParent, WinBits nWinStyle)
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
:OListboxControl_Base( PropertyControlType::ListBox, pParent, nWinStyle )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->SetDropDownLineCount( LB_DEFAULT_COUNT );
|
2007-05-10 09:50:15 +00:00
|
|
|
if ( ( nWinStyle & WB_READONLY ) != 0 )
|
|
|
|
{
|
2015-08-12 15:09:57 +02:00
|
|
|
getTypedControlWindow()->SetReadOnly();
|
2015-10-19 17:49:57 +02:00
|
|
|
getTypedControlWindow()->Enable();
|
2007-05-10 09:50:15 +00:00
|
|
|
}
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Any SAL_CALL OListboxControl::getValue()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2017-09-14 16:50:25 +02:00
|
|
|
OUString sControlValue( getTypedControlWindow()->GetSelectedEntry() );
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
Any aPropValue;
|
2011-12-22 15:35:41 -02:00
|
|
|
if ( !sControlValue.isEmpty() )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
aPropValue <<= sControlValue;
|
|
|
|
return aPropValue;
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Type SAL_CALL OListboxControl::getValueType()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-05-11 10:09:04 +02:00
|
|
|
return ::cppu::UnoType<OUString>::get();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OListboxControl::setValue( const Any& _rValue )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( !_rValue.hasValue() )
|
|
|
|
getTypedControlWindow()->SetNoSelection();
|
|
|
|
else
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2013-04-07 12:06:47 +02:00
|
|
|
OUString sSelection;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
_rValue >>= sSelection;
|
|
|
|
|
2017-09-14 16:50:25 +02:00
|
|
|
if ( sSelection != getTypedControlWindow()->GetSelectedEntry() )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->SelectEntry( sSelection );
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( !getTypedControlWindow()->IsEntrySelected( sSelection ) )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->InsertEntry( sSelection, 0 );
|
|
|
|
getTypedControlWindow()->SelectEntry( sSelection );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OListboxControl::clearList()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->Clear();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OListboxControl::prependListEntry( const OUString& NewEntry )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->InsertEntry( NewEntry, 0 );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OListboxControl::appendListEntry( const OUString& NewEntry )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->InsertEntry( NewEntry );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Sequence< OUString > SAL_CALL OListboxControl::getListEntries( )
|
2007-07-06 07:54:12 +00:00
|
|
|
{
|
2015-08-30 23:08:29 +02:00
|
|
|
const sal_Int32 nCount = getTypedControlWindow()->GetEntryCount();
|
2013-04-07 12:06:47 +02:00
|
|
|
Sequence< OUString > aRet(nCount);
|
|
|
|
OUString* pIter = aRet.getArray();
|
2015-08-30 23:08:29 +02:00
|
|
|
for (sal_Int32 i = 0; i < nCount ; ++i,++pIter)
|
2007-07-06 07:54:12 +00:00
|
|
|
*pIter = getTypedControlWindow()->GetEntry(i);
|
|
|
|
|
|
|
|
return aRet;
|
|
|
|
}
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2015-10-09 17:44:20 +02:00
|
|
|
void OListboxControl::setModified()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2015-10-09 17:44:20 +02:00
|
|
|
OListboxControl_Base::setModified();
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( !getTypedControlWindow()->IsTravelSelect() )
|
2001-01-12 10:35:45 +00:00
|
|
|
// fire a commit
|
2015-10-09 15:17:24 +02:00
|
|
|
notifyModifiedValue();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
//= OComboboxControl
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
OComboboxControl::OComboboxControl( vcl::Window* pParent, WinBits nWinStyle)
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
:OComboboxControl_Base( PropertyControlType::ComboBox, pParent, nWinStyle )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->SetDropDownLineCount( LB_DEFAULT_COUNT );
|
CWS-TOOLING: integrate CWS dba32a
2009-04-16 13:08:19 +0200 oj r270882 : #i14538# set property at control
2009-04-16 13:04:28 +0200 oj r270881 : #i98557# remove binary string for SRB
2009-04-15 13:19:10 +0200 oj r270838 : #i96782# use type set at view
2009-04-14 14:53:20 +0200 oj r270778 : #i96782# set initialize size for custom shape
2009-04-06 14:19:14 +0200 oj r270546 : #i88432# correct pos when < 0 while resizing
2009-04-06 13:36:13 +0200 oj r270541 : #i96782# handle toolbar and menubar differently
2009-04-06 13:33:54 +0200 oj r270540 : #i96782# handle toolbar and menubar differently
2009-04-06 12:28:23 +0200 oj r270534 : #i96782# handle toolbar and menubar differently
2009-04-06 12:27:44 +0200 oj r270533 : #i96782# handle toolbar and menubar differently
2009-04-06 12:24:32 +0200 oj r270532 : #i96782# handle toolbar and menubar differently
2009-04-06 12:15:15 +0200 oj r270531 : do not initialze when field is empty
2009-04-06 10:06:08 +0200 oj r270528 : #i96782# clean up of menubar and remove duplicates
2009-04-06 09:47:49 +0200 oj r270527 : #i96519# adjust help text dynamic
2009-04-03 13:43:20 +0200 oj r270482 : do not need to remove section from observer they are already disposed
2009-04-03 13:27:28 +0200 fs r270479 : #i97356#
2009-04-02 11:30:39 +0200 fs r270386 : UNX line ends
2009-04-02 10:54:51 +0200 fs r270379 : UNX line ends
2009-04-02 10:39:57 +0200 fs r270378 : UNX line ends
2009-04-02 10:37:24 +0200 fs r270377 : why did this survive the rebase? was removed on trunk ...
2009-03-31 13:31:12 +0200 fs r270277 : component_foo should be public
2009-03-28 00:21:01 +0100 fs r270176 : manuallly merged the changes which happened in CWS before resync to m45, where the directory had been moved from reportdesign/registry to reportbuilder/registry
2009-03-27 23:01:20 +0100 fs r270174 : CWS-TOOLING: rebase CWS dba32a to trunk@270033 (milestone: DEV300:m45)
2009-03-11 12:23:35 +0100 fs r269310 : #i99958# ensure the ControlModelLock doesn't release twice
2009-03-06 09:07:32 +0100 fs r268970 : ignore output paths in SVN's status
2009-03-06 09:07:08 +0100 fs r268969 : ignore output paths in SVN's status
2009-03-04 11:28:02 +0100 oj r268800 : copy and paste error, check correct end now
2009-03-03 15:49:11 +0100 fs r268736 : #i10000# those merges were lost during the rebase (m38->m42)
2009-03-03 13:25:27 +0100 lla r268720 : #i99652# fix wrong refactoring
2009-02-27 11:12:56 +0100 fs r268566 : beautified
2009-02-27 10:53:47 +0100 fs r268561 : doFormListening(false) only when actually isFormListening() (found during complex test case XMLFormSettings with assertions)
2009-02-26 20:55:31 +0100 fs r268546 : #i96530# set the Label property of the bound control, if we didn't create a dedicated label control
2009-02-26 11:53:09 +0100 fs r268494 : #i10000#
2009-02-26 11:27:50 +0100 fs r268493 : #i10000#
2009-02-26 11:17:08 +0100 fs r268490 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-25 11:39:48 +0100 fs r268422 : #i10000# post-resync: INFO_ESCAPE_DATETIME got lost during rebase
2009-02-24 23:24:10 +0100 fs r268411 : CWS-TOOLING: rebase CWS dba32a to trunk@268395 (milestone: DEV300:m42)
2009-02-20 15:09:48 +0100 fs r268324 : respect ImplicitCatalog/SchemaRestriction in all necessary places
2009-02-20 13:48:10 +0100 oj r268318 : order of initialize corrected
2009-02-14 15:07:52 +0100 fs r267759 : #i98975# when an image does not have a bitmap, but a text, draw this (as placeholder)
2009-02-14 15:02:40 +0100 fs r267758 : consolidated and removed some duplicate code
2009-02-14 13:52:23 +0100 fs r267756 : #i10000#
2009-02-13 22:08:34 +0100 fs r267750 : #i100000#
2009-02-13 22:07:25 +0100 fs r267749 : #i10000#
2009-02-13 21:55:36 +0100 fs r267747 : #i10000#
2009-02-13 21:54:27 +0100 fs r267746 : use const_cast
2009-02-13 21:29:10 +0100 fs r267745 : #i10000#
2009-02-13 21:27:39 +0100 fs r267744 : #i10000#
2009-02-13 20:59:13 +0100 fs r267742 : #i10000#
2009-02-13 13:21:30 +0100 fs r267717 : better diagnostics
2009-02-13 13:17:24 +0100 fs r267715 : #i58313# support Catalog/SchemaRestriction settings, which are applied in getTables when 'all catalogs/schemas' are to be retrieved
2009-02-13 13:16:14 +0100 fs r267714 : filter out some more known global settings
2009-02-13 12:39:43 +0100 fs r267713 : #i58313# ImplicitCatalog/SchemaRestriction
2009-02-13 12:36:50 +0100 fs r267712 : when exporting data source settings, allow for properties which have a VOID default value, but are currently not VOID
2009-02-13 12:35:57 +0100 fs r267711 : implement XSet, to allow inserting properties which have a default value of VOID
2009-02-13 12:35:03 +0100 fs r267710 : +addVoidProperty
2009-02-13 10:20:08 +0100 fs r267697 : removed unused variable
2009-02-13 09:46:46 +0100 fs r267695 : refactored the table filtering code, to have a better base for introducing additional low level filters
2009-02-10 09:23:07 +0100 lla r267537 : #i10000# wrong line feed, double named variable
2009-02-09 12:13:08 +0100 oj r267508 : #i98605# notify hanlder
2009-02-09 11:50:34 +0100 oj r267507 : #i98926# solve refcount problem
2009-02-09 11:50:05 +0100 oj r267506 : #i98971# fix for simple html
2009-02-09 11:49:24 +0100 oj r267505 : #i98971# fix for simple html
2009-02-09 11:47:27 +0100 oj r267504 : invoke on copy
2009-02-09 09:51:00 +0100 fs r267500 : #i98316#
2009-02-09 09:46:10 +0100 fs r267499 : setCurrentSelection: don't reset the current form when we de-select everything
2009-02-09 09:43:45 +0100 fs r267498 : #i98316#
2009-02-08 21:25:18 +0100 fs r267496 : #i98272# introduce late ctor for cloning
2009-02-07 21:08:39 +0100 fs r267485 : #i98272# when copy-constructing a FmFormPageImpl, use the XCloneable of the forms collection, instead of XPersistObject (which is incompletely implemented)
2009-02-07 21:07:26 +0100 fs r267484 : removed obsolete include guards
2009-02-07 21:05:22 +0100 fs r267483 : #i98272# implement XCloneable
2009-02-06 15:02:48 +0100 lla r267467 : #i96523# add XImageControl
2009-02-06 14:41:38 +0100 oj r267463 : #i98926# late init when connection disposed but only when asked for
2009-02-06 13:49:57 +0100 lla r267457 : #i92860# bigint in forms doesn't allow input of values > 1, fixed
2009-02-06 13:03:55 +0100 oj r267455 : ImageScaleMode
2009-02-05 14:48:19 +0100 lla r267424 : #i89335# dropdown listboxes are 14 instead of 7 lines high
2009-02-05 13:40:00 +0100 oj r267423 : #i96945# insert new prop Opaque
2009-02-05 13:39:19 +0100 oj r267422 : #i96945# insert layer handling for hell and heaven
2009-02-05 13:29:32 +0100 lla r267420 : #i89335# add is null, is not null, is not like filter condition
2009-02-04 12:23:02 +0100 oj r267364 : #i98821# load table font settings
2009-02-04 10:05:27 +0100 oj r267351 : #i98821# load table font settings
2009-02-04 09:23:22 +0100 fs r267350 : checking persistency of UI settings in database documents - for the moment, capture table formattings (which is issue 98821)
2009-02-04 09:22:15 +0100 fs r267349 : moved some methods which are of wider interest from DatabaseDocument to FileHelper resp. TestCase
2009-02-04 08:56:27 +0100 oj r267347 : #i97586# UcbStreamHelper::CreateStream doesn't check all streamModes use different method
2009-02-04 08:23:26 +0100 oj r267346 : #i98701# check key size is >= 3 and some redesign
2009-02-03 23:29:24 +0100 fs r267345 : return the component (controller), not the frame
2009-02-03 23:28:53 +0100 fs r267344 : openExisting returns a controller now, not the frame (this was a bug)
2009-02-03 23:28:25 +0100 fs r267343 : openElement: properly return the component in the table/query case
2009-02-02 12:48:17 +0100 oj r267261 : #i96013# fix for relative path
2009-02-02 10:33:28 +0100 lla r267253 : #i98557# cleanups and consolidation
2009-02-02 09:37:23 +0100 lla r267250 : #i88432# resize will no longer move components to other sections
2009-02-02 09:08:24 +0100 oj r267245 : #i97475# write 0x1A at the end of the file
2009-01-30 19:39:20 +0100 lla r267230 : #i10000# unused parameters
2009-01-30 09:51:09 +0100 fs r267181 : onsolete
2009-01-30 09:49:27 +0100 fs r267180 : onsolete
2009-01-29 14:28:22 +0100 oj r267139 : #i96825# import cell style
2009-01-29 14:23:12 +0100 oj r267137 : #i98601# export imagescalehandler
2009-01-29 14:19:57 +0100 lla r267135 : #i98601# add ImageScaleMode
2009-01-29 13:21:08 +0100 oj r267124 : #i98601# impl ScaleMode
2009-01-29 13:20:56 +0100 oj r267123 : #i98601# impl ScaleMode
2009-01-29 08:46:40 +0100 oj r267095 : new property: ScaleMode
2009-01-29 08:45:23 +0100 oj r267094 : new ScaleMode from UnControlImageModel
2009-01-29 08:28:12 +0100 oj r267093 : #i87930# close all sub forms/reports when the desktop is going to be terminated and no db frame exists
2009-01-28 19:54:34 +0100 lla r267082 : #i98557# pictures in report wizard
2009-01-28 15:06:25 +0100 oj r267060 : #i87930# close all sub forms/reports when the desktop is going to be terminated and no db frame exists
2009-01-28 11:38:41 +0100 lla r267046 : #i76783# handle binary fields in forms
2009-01-28 09:24:43 +0100 lla r267025 : #i10000#
2009-01-28 08:40:04 +0100 fs r267024 : #i10000#
2009-01-28 08:04:43 +0100 oj r267023 : #i93456# use resource strings for function names
2009-01-27 13:26:05 +0100 oj r266988 : check data field is type field or expression
2009-01-27 13:07:17 +0100 oj r266985 : check data field length
2009-01-27 11:48:19 +0100 oj r266974 : #i96823# return dll string as column name when no alias exists
2009-01-27 09:53:11 +0100 fs r266958 : display the message of a caught exception
2009-01-27 09:44:13 +0100 fs r266957 : #i58313# when retrieving all tables, just set an empty table type filter - the connection will care for translating this, by respecting the TableTypeFilterMode setting
2009-01-27 09:36:09 +0100 fs r266956 : #i58313# getTables: per JDBC spec, is not a valid table type filter. Translate it to 'null'.
2009-01-26 11:24:49 +0100 lla r266912 : #i97865# cleanups (AddField viewable in remote mode)
2009-01-26 07:49:27 +0100 lla r266897 : #i97865# AddField opens in remote case
2009-01-26 07:48:58 +0100 lla r266896 : #i97865# AddField opens in remote case
2009-01-26 07:48:42 +0100 lla r266895 : #i97865# AddField opens in remote case
2009-01-23 15:04:40 +0100 fs r266825 : consolidate the usage of OSQLMessageBox with MessageType==Warning into OSQLWarningBox
2009-01-23 10:47:33 +0100 fs r266787 : +supportsUserAdministration
2009-01-23 10:47:11 +0100 fs r266784 : use DatabaseMetaData.supportsUserAdministration
2009-01-23 07:55:59 +0100 lla r266767 : #i10000# fix gcc compiler failures
2009-01-21 15:08:55 +0100 lla r266673 : #i97265# Labels in HC (IsDark) with other color (viewable)
2009-01-19 14:58:54 +0100 lla r266504 : #i96523# last problems with FormatKey and '0' values fixed
2009-01-19 14:58:00 +0100 lla r266503 : #i96519# AddField help text
2009-01-19 11:59:02 +0100 fs r266485 : #i96523# for formatted field models, init them with TreatAsNumber = false
2009-01-16 10:31:49 +0100 lla r266405 : #i96793# add shrink to popup menu
2009-01-16 09:21:44 +0100 lla r266401 : #i96519# AddField contains a help text
2009-01-15 11:21:49 +0100 lla r266357 : #i96523# problem with XVclWindowPeer not fixed now
2009-01-15 09:19:20 +0100 lla r266335 : #i96523# more crashes fixed.
2009-01-14 13:08:34 +0100 lla r266291 : #i96523# problems with crashes fixed
2009-01-13 10:54:24 +0100 lla r266199 : #i96523# show datasource in formattedfields new files
2009-01-13 10:52:39 +0100 lla r266198 : #i96523# show datasource in formattedfields
2009-01-13 09:41:50 +0100 lla r266197 : #i96526# handling none existance default.otr
2009-01-12 12:55:49 +0100 fs r266151 : don't expect the control model to be a BoundComponent before adding as modify listener
2009-01-12 12:51:33 +0100 fs r266149 : #i88458# let the ImageControl be an XModifyBroadcaster, so the forms runtime can notice when the user changes the control content while it does not have the focus
2009-01-09 13:41:22 +0100 fs r266080 : doc
2009-01-09 13:14:14 +0100 fs r266077 : #i97377# SetModified when order is changed via DnD
2009-01-07 09:55:40 +0100 oj r265951 : merge from master
2009-01-07 09:55:24 +0100 oj r265950 : removed observer
2009-01-07 09:55:06 +0100 oj r265949 : merge from master
2009-01-07 07:29:11 +0100 oj r265945 : shadow var changed
2009-01-06 07:25:57 +0100 oj r265893 : CWS-TOOLING: rebase CWS dba32a to trunk@265758 (milestone: DEV300:m38)
2009-01-05 13:18:22 +0100 oj r265865 : convert to unix le
2009-01-05 09:13:52 +0100 lla r265857 : #i79423# lc_ sc_ permutation fix
2009-01-02 19:40:59 +0100 lla r265847 : #i79423# section shrink icons
2008-12-22 11:37:57 +0100 lla r265749 : #i97484# move component to negative Y-position
2008-12-22 11:37:05 +0100 lla r265748 : #i97484# move component to negative Y-position
2008-12-22 11:35:33 +0100 lla r265747 : #i97484# move component to negative Y-position
2008-12-22 11:25:07 +0100 lla r265745 : #i96757# changes via property browser was not undoable
2008-12-18 15:10:38 +0100 fs r265694 : corrected an condition in doFormListening, which otherwise leads to uncommitable grid columns in documents which are loaded from disc (not in documents which are newly created)
2008-12-18 14:54:39 +0100 fs r265692 : Hide Columns text slightly changed
2008-12-18 13:44:15 +0100 fs r265683 : #i94068# properly display erros happening during a form operation - at least once, and at most once
2008-12-18 11:28:29 +0100 fs r265677 : document the new InputRequired property
2008-12-18 11:04:15 +0100 fs r265676 : #i96530# createControlLabelPair: don't actually create a label for a checkbox
2008-12-18 10:35:53 +0100 fs r265674 : #i95226# when a column is replaced, and it's the selected column, update the selection
2008-12-18 10:34:42 +0100 fs r265673 : #i95226# refactoring of the implReplaced method
2008-12-18 10:34:28 +0100 fs r265672 : #i95226# when replacing a grid column, update the property browser
2008-12-18 10:33:17 +0100 fs r265671 : when an element is removed, remove it from m_aCurrentSelection, too (if necessary)
2008-12-18 10:31:57 +0100 fs r265670 : Hide Columns text slightly changed
2008-12-18 10:15:56 +0100 lla r265669 : #i14538# do not allow to press finish button twice
2008-12-18 08:56:33 +0100 lla r265665 : #i10000# build depend=t problem hacked.
2008-12-17 20:59:10 +0100 fs r265656 : #i89821# don't let a MultiLineEdit select all text when it receives the focus
2008-12-17 12:10:54 +0100 fs r265594 : #i97356#
2008-12-17 12:06:29 +0100 fs r265593 : #i97355# Print -> Printable
2008-12-17 11:59:31 +0100 fs r265591 : #i97350# combo boxes comment on list selection (as list boxes already do)
2008-12-16 09:53:57 +0100 lla r265527 : #i96526# handling none existance default.otr
2008-12-15 14:48:39 +0100 lla r265500 : #i79423# reparing, was wrong implemented
2008-12-12 15:08:33 +0100 lla r265424 : #i10000# remove wrong carridge returns
2008-12-12 15:07:55 +0100 lla r265423 : #i10000# remove wrong carridge returns
2008-12-12 15:06:41 +0100 lla r265422 : #i10000# remove wrong carridge returns
2008-12-12 10:23:13 +0100 lla r265395 : #i95234# reset DragDelta
2008-12-12 10:11:02 +0100 lla r265393 : #i79423# pre versions of shrink buttons
2008-12-11 15:32:13 +0100 fs r265318 : prevent a deadlock during complex.dbaccess.DatabaseDocument test
2008-12-11 15:30:06 +0100 fs r265316 : prevent a deadlock during complex.dbaccess.DatabaseDocument test
2008-12-11 15:07:05 +0100 fs r265307 : removed superfluous text
2008-12-11 12:29:54 +0100 lla r265282 : #i96757# cleanup second try
2008-12-11 12:09:15 +0100 lla r265278 : #i96757# cleanup
2008-12-11 12:07:56 +0100 lla r265277 : #i95234#
2008-12-10 14:04:39 +0100 lla r265183 : #i93472# D&D fixes
2008-12-10 12:29:33 +0100 lla r265168 : #i94067# add (APP|SYS)FONT to XUnitConversion
2008-12-10 12:15:02 +0100 lla r265166 : #i94067# add APPFONT, SYSFONT to MeasureUnit
2008-12-10 11:52:10 +0100 lla r265163 : #i94067# add comments
2008-12-06 20:33:05 +0100 fs r264935 : #i10000# precompiled header
2008-12-05 09:29:26 +0100 fs r264889 : #i10000#
2008-12-05 09:07:31 +0100 fs r264888 : #i10000#
2008-12-04 13:25:46 +0100 fs r264838 : CWS-TOOLING: rebase CWS dba32a to trunk@264807 (milestone: DEV300:m37)
2008-12-03 23:49:13 +0100 fs r264808 : merge changes from trunk, to be able to do a rebase
2008-12-03 17:13:09 +0100 lla r264801 : #i91041# update documentation
2008-12-03 16:57:04 +0100 lla r264799 : #i94067# allow convert(Point|Size)ToLogic as pixel also
2008-12-02 12:36:32 +0100 lla r264687 : #i96782# bring toolbar objects to menu structure
2008-12-02 10:32:44 +0100 lla r264667 : #i86255# make property work
2008-12-02 09:22:47 +0100 lla r264659 : #i79423# add section shrink toolbar
2008-12-02 07:41:22 +0100 lla r264657 : #i86255# add check box for Escape DateTime property
2008-12-02 07:37:17 +0100 lla r264656 : #i79423# new shrink buttons
2008-11-26 11:55:28 +0100 fs r264362 : #i96541#
FillPropertySet: do not only catch UnknownPropertyException when setting the Char/ParaAutoStyleName,
but also care for the other exceptions which can be thrown by XPropertySet::setPropertyValue.
This is actually not the real fix for #i96541#, but only a follow-up. The root cause of the issue
was fixed in CWS dba301b, but this here was another (potential) bug which popped up during investigations.
2008-11-25 09:04:40 +0100 lla r264273 : #i82083# new toolbox in GroupsSorting dialog
2008-11-25 08:56:08 +0100 lla r264272 : #i94729# change token strings into string list, move class out of function
2008-11-24 15:52:22 +0100 fs r264251 : #i96532# do not set AppendTableAlias, NameLengthLimit, etc., if the OXMLDataSourceInstance is used for elements at which those attributes never appear
2008-11-24 15:51:45 +0100 fs r264249 : #i96532# do not set AppendTableAlias, NameLengthLimit, etc., if the OXMLDataSourceInstance is used for elements at which those attributes never appear
2008-11-24 15:45:21 +0100 fs r264244 : #i96532# the API default for ParamNameSubst is false
2008-11-24 15:45:04 +0100 fs r264243 : #i96532# do not set AppendTableAlias, NameLengthLimit, etc., if the OXMLDataSourceInstance is used for elements at which those attributes never appear
2008-11-24 15:44:14 +0100 fs r264241 : #i96532# slight refactoring of exporting properties which have a XML default different from the API default
2008-11-24 10:50:01 +0100 lla r264216 : #i82083# icons for new toolbox
2008-11-24 09:38:45 +0100 lla r264205 : #i82083# new toolbox in GroupsSorting dialog
2008-11-24 09:32:20 +0100 lla r264201 : #i96501# cleanup assertions
2008-11-24 09:12:55 +0100 lla r264198 : #i83082# enhancement for toolboxes, better HC comfort
2008-11-24 08:46:43 +0100 lla r264197 : #i96501# fix problem with negative positions
2008-11-21 11:44:47 +0100 fs r264118 : #i57042# introduce a counter for suspending change notifications of a given property, so recursive calls are possible
2008-11-21 11:02:17 +0100 fs r264116 : #i96388# don't call ExecuteContextMenuAction when no action was chosen by the user
2008-11-21 10:36:53 +0100 fs r264114 : #i47384# assertion was wrong
2008-11-14 12:33:15 +0100 fs r263673 : #i47318# XRowSetChangeBroadcaster/Listener, to be able to listen for changes in an XRowSetSupplier's RowSet
2008-11-14 12:30:29 +0100 fs r263672 : #i47318# more refactoring
- BoundControlModels now listen at the XRowSetSupplier for changes in the supplied
RowSet, to properly revoke/register old/new listeners at the RowSet
- replaced ::osl::Mutex in various places with a ControlModelLock
2008-11-14 12:20:55 +0100 fs r263671 : when BUILD_TYPE includes QADEVOOO, the BUILD_QADEVOOO needs to bet set, too
2008-11-14 12:19:21 +0100 fs r263670 : oops, this was not intended to be committed
2008-11-12 11:08:10 +0100 fs r263579 : #i96096# new ctors taking UNO_QUERY_THROW
2008-11-12 09:15:54 +0100 fs r263576 : no need to load the complete dialog just to get a string which the dialog itself loads from resource
2008-11-10 17:55:45 +0100 fs r263535 : spelling in comment
2008-11-10 15:51:14 +0100 fs r263523 : #i47318# various refactorings
1. don't forward syntetic XLoadListener events from the grid control to
the grid columns. Instead, forward GridColumn::XChild::setParent to
the base class, which then can add itself as load listener
2. removed various occurances of XMultiServiceFactory, instead use the
::comphelper::ComponentContext
3. in O(Bound)ControlModel, have a mechanism to lock the instance (using
ControlModelLock) and fire property changes when the last lock dies.
2008-11-10 12:49:24 +0100 oj r263513 : #i94729# change token strings into string list
2008-11-10 12:13:15 +0100 oj r263512 : #i95222# export chart:title style as well
2008-11-10 08:55:25 +0100 oj r263507 : #i93471# show the correct tabpage when selecting a different object
2008-11-07 23:38:29 +0100 fs r263490 : #i95977# for the event input controls, add a component extending their functionality so they're reset when the users presses DEL
2008-11-07 23:35:39 +0100 fs r263489 : during #i95977#: When a VCL Window is deleted from within VCL code, the respective WindowPeer was never disposed. Corrected this.
2008-11-07 14:57:07 +0100 fs r263420 : #i95963# human-readable display names for event bindings
2008-11-06 10:34:52 +0100 fs r263366 : #i95865# don't use library names containing InvalidZipEntryFileNames - workaround until i95409 is fixed
2008-11-06 10:33:28 +0100 fs r263365 : #i95865#
copied the following change from CWS odfmetadata2 (not yet integrated) into CWS dba31d
- comphelper/inc/comphelper/storagehelper.hxx,
comphelper/source/misc/storagehelper.cxx:
+ add function IsValidZipEntryFileName (moved from module package)
2009-04-22 11:01:27 +00:00
|
|
|
getTypedControlWindow()->SetSelectHdl( LINK( this, OComboboxControl, OnEntrySelected ) );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OComboboxControl::setValue( const Any& _rValue )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2013-04-07 12:06:47 +02:00
|
|
|
OUString sText;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
_rValue >>= sText;
|
|
|
|
getTypedControlWindow()->SetText( sText );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Any SAL_CALL OComboboxControl::getValue()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2017-05-19 17:18:13 +02:00
|
|
|
return makeAny( getTypedControlWindow()->GetText() );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Type SAL_CALL OComboboxControl::getValueType()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-05-11 10:09:04 +02:00
|
|
|
return ::cppu::UnoType<OUString>::get();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OComboboxControl::clearList()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->Clear();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OComboboxControl::prependListEntry( const OUString& NewEntry )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->InsertEntry( NewEntry, 0 );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OComboboxControl::appendListEntry( const OUString& NewEntry )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->InsertEntry( NewEntry );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Sequence< OUString > SAL_CALL OComboboxControl::getListEntries( )
|
2007-07-06 07:54:12 +00:00
|
|
|
{
|
2015-08-30 23:08:29 +02:00
|
|
|
const sal_Int32 nCount = getTypedControlWindow()->GetEntryCount();
|
2013-04-07 12:06:47 +02:00
|
|
|
Sequence< OUString > aRet(nCount);
|
|
|
|
OUString* pIter = aRet.getArray();
|
2015-08-30 23:08:29 +02:00
|
|
|
for (sal_Int32 i = 0; i < nCount ; ++i,++pIter)
|
2007-07-06 07:54:12 +00:00
|
|
|
*pIter = getTypedControlWindow()->GetEntry(i);
|
|
|
|
|
|
|
|
return aRet;
|
|
|
|
}
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2016-10-05 07:56:12 +02:00
|
|
|
IMPL_LINK_NOARG( OComboboxControl, OnEntrySelected, ComboBox&, void )
|
CWS-TOOLING: integrate CWS dba32a
2009-04-16 13:08:19 +0200 oj r270882 : #i14538# set property at control
2009-04-16 13:04:28 +0200 oj r270881 : #i98557# remove binary string for SRB
2009-04-15 13:19:10 +0200 oj r270838 : #i96782# use type set at view
2009-04-14 14:53:20 +0200 oj r270778 : #i96782# set initialize size for custom shape
2009-04-06 14:19:14 +0200 oj r270546 : #i88432# correct pos when < 0 while resizing
2009-04-06 13:36:13 +0200 oj r270541 : #i96782# handle toolbar and menubar differently
2009-04-06 13:33:54 +0200 oj r270540 : #i96782# handle toolbar and menubar differently
2009-04-06 12:28:23 +0200 oj r270534 : #i96782# handle toolbar and menubar differently
2009-04-06 12:27:44 +0200 oj r270533 : #i96782# handle toolbar and menubar differently
2009-04-06 12:24:32 +0200 oj r270532 : #i96782# handle toolbar and menubar differently
2009-04-06 12:15:15 +0200 oj r270531 : do not initialze when field is empty
2009-04-06 10:06:08 +0200 oj r270528 : #i96782# clean up of menubar and remove duplicates
2009-04-06 09:47:49 +0200 oj r270527 : #i96519# adjust help text dynamic
2009-04-03 13:43:20 +0200 oj r270482 : do not need to remove section from observer they are already disposed
2009-04-03 13:27:28 +0200 fs r270479 : #i97356#
2009-04-02 11:30:39 +0200 fs r270386 : UNX line ends
2009-04-02 10:54:51 +0200 fs r270379 : UNX line ends
2009-04-02 10:39:57 +0200 fs r270378 : UNX line ends
2009-04-02 10:37:24 +0200 fs r270377 : why did this survive the rebase? was removed on trunk ...
2009-03-31 13:31:12 +0200 fs r270277 : component_foo should be public
2009-03-28 00:21:01 +0100 fs r270176 : manuallly merged the changes which happened in CWS before resync to m45, where the directory had been moved from reportdesign/registry to reportbuilder/registry
2009-03-27 23:01:20 +0100 fs r270174 : CWS-TOOLING: rebase CWS dba32a to trunk@270033 (milestone: DEV300:m45)
2009-03-11 12:23:35 +0100 fs r269310 : #i99958# ensure the ControlModelLock doesn't release twice
2009-03-06 09:07:32 +0100 fs r268970 : ignore output paths in SVN's status
2009-03-06 09:07:08 +0100 fs r268969 : ignore output paths in SVN's status
2009-03-04 11:28:02 +0100 oj r268800 : copy and paste error, check correct end now
2009-03-03 15:49:11 +0100 fs r268736 : #i10000# those merges were lost during the rebase (m38->m42)
2009-03-03 13:25:27 +0100 lla r268720 : #i99652# fix wrong refactoring
2009-02-27 11:12:56 +0100 fs r268566 : beautified
2009-02-27 10:53:47 +0100 fs r268561 : doFormListening(false) only when actually isFormListening() (found during complex test case XMLFormSettings with assertions)
2009-02-26 20:55:31 +0100 fs r268546 : #i96530# set the Label property of the bound control, if we didn't create a dedicated label control
2009-02-26 11:53:09 +0100 fs r268494 : #i10000#
2009-02-26 11:27:50 +0100 fs r268493 : #i10000#
2009-02-26 11:17:08 +0100 fs r268490 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-25 11:39:48 +0100 fs r268422 : #i10000# post-resync: INFO_ESCAPE_DATETIME got lost during rebase
2009-02-24 23:24:10 +0100 fs r268411 : CWS-TOOLING: rebase CWS dba32a to trunk@268395 (milestone: DEV300:m42)
2009-02-20 15:09:48 +0100 fs r268324 : respect ImplicitCatalog/SchemaRestriction in all necessary places
2009-02-20 13:48:10 +0100 oj r268318 : order of initialize corrected
2009-02-14 15:07:52 +0100 fs r267759 : #i98975# when an image does not have a bitmap, but a text, draw this (as placeholder)
2009-02-14 15:02:40 +0100 fs r267758 : consolidated and removed some duplicate code
2009-02-14 13:52:23 +0100 fs r267756 : #i10000#
2009-02-13 22:08:34 +0100 fs r267750 : #i100000#
2009-02-13 22:07:25 +0100 fs r267749 : #i10000#
2009-02-13 21:55:36 +0100 fs r267747 : #i10000#
2009-02-13 21:54:27 +0100 fs r267746 : use const_cast
2009-02-13 21:29:10 +0100 fs r267745 : #i10000#
2009-02-13 21:27:39 +0100 fs r267744 : #i10000#
2009-02-13 20:59:13 +0100 fs r267742 : #i10000#
2009-02-13 13:21:30 +0100 fs r267717 : better diagnostics
2009-02-13 13:17:24 +0100 fs r267715 : #i58313# support Catalog/SchemaRestriction settings, which are applied in getTables when 'all catalogs/schemas' are to be retrieved
2009-02-13 13:16:14 +0100 fs r267714 : filter out some more known global settings
2009-02-13 12:39:43 +0100 fs r267713 : #i58313# ImplicitCatalog/SchemaRestriction
2009-02-13 12:36:50 +0100 fs r267712 : when exporting data source settings, allow for properties which have a VOID default value, but are currently not VOID
2009-02-13 12:35:57 +0100 fs r267711 : implement XSet, to allow inserting properties which have a default value of VOID
2009-02-13 12:35:03 +0100 fs r267710 : +addVoidProperty
2009-02-13 10:20:08 +0100 fs r267697 : removed unused variable
2009-02-13 09:46:46 +0100 fs r267695 : refactored the table filtering code, to have a better base for introducing additional low level filters
2009-02-10 09:23:07 +0100 lla r267537 : #i10000# wrong line feed, double named variable
2009-02-09 12:13:08 +0100 oj r267508 : #i98605# notify hanlder
2009-02-09 11:50:34 +0100 oj r267507 : #i98926# solve refcount problem
2009-02-09 11:50:05 +0100 oj r267506 : #i98971# fix for simple html
2009-02-09 11:49:24 +0100 oj r267505 : #i98971# fix for simple html
2009-02-09 11:47:27 +0100 oj r267504 : invoke on copy
2009-02-09 09:51:00 +0100 fs r267500 : #i98316#
2009-02-09 09:46:10 +0100 fs r267499 : setCurrentSelection: don't reset the current form when we de-select everything
2009-02-09 09:43:45 +0100 fs r267498 : #i98316#
2009-02-08 21:25:18 +0100 fs r267496 : #i98272# introduce late ctor for cloning
2009-02-07 21:08:39 +0100 fs r267485 : #i98272# when copy-constructing a FmFormPageImpl, use the XCloneable of the forms collection, instead of XPersistObject (which is incompletely implemented)
2009-02-07 21:07:26 +0100 fs r267484 : removed obsolete include guards
2009-02-07 21:05:22 +0100 fs r267483 : #i98272# implement XCloneable
2009-02-06 15:02:48 +0100 lla r267467 : #i96523# add XImageControl
2009-02-06 14:41:38 +0100 oj r267463 : #i98926# late init when connection disposed but only when asked for
2009-02-06 13:49:57 +0100 lla r267457 : #i92860# bigint in forms doesn't allow input of values > 1, fixed
2009-02-06 13:03:55 +0100 oj r267455 : ImageScaleMode
2009-02-05 14:48:19 +0100 lla r267424 : #i89335# dropdown listboxes are 14 instead of 7 lines high
2009-02-05 13:40:00 +0100 oj r267423 : #i96945# insert new prop Opaque
2009-02-05 13:39:19 +0100 oj r267422 : #i96945# insert layer handling for hell and heaven
2009-02-05 13:29:32 +0100 lla r267420 : #i89335# add is null, is not null, is not like filter condition
2009-02-04 12:23:02 +0100 oj r267364 : #i98821# load table font settings
2009-02-04 10:05:27 +0100 oj r267351 : #i98821# load table font settings
2009-02-04 09:23:22 +0100 fs r267350 : checking persistency of UI settings in database documents - for the moment, capture table formattings (which is issue 98821)
2009-02-04 09:22:15 +0100 fs r267349 : moved some methods which are of wider interest from DatabaseDocument to FileHelper resp. TestCase
2009-02-04 08:56:27 +0100 oj r267347 : #i97586# UcbStreamHelper::CreateStream doesn't check all streamModes use different method
2009-02-04 08:23:26 +0100 oj r267346 : #i98701# check key size is >= 3 and some redesign
2009-02-03 23:29:24 +0100 fs r267345 : return the component (controller), not the frame
2009-02-03 23:28:53 +0100 fs r267344 : openExisting returns a controller now, not the frame (this was a bug)
2009-02-03 23:28:25 +0100 fs r267343 : openElement: properly return the component in the table/query case
2009-02-02 12:48:17 +0100 oj r267261 : #i96013# fix for relative path
2009-02-02 10:33:28 +0100 lla r267253 : #i98557# cleanups and consolidation
2009-02-02 09:37:23 +0100 lla r267250 : #i88432# resize will no longer move components to other sections
2009-02-02 09:08:24 +0100 oj r267245 : #i97475# write 0x1A at the end of the file
2009-01-30 19:39:20 +0100 lla r267230 : #i10000# unused parameters
2009-01-30 09:51:09 +0100 fs r267181 : onsolete
2009-01-30 09:49:27 +0100 fs r267180 : onsolete
2009-01-29 14:28:22 +0100 oj r267139 : #i96825# import cell style
2009-01-29 14:23:12 +0100 oj r267137 : #i98601# export imagescalehandler
2009-01-29 14:19:57 +0100 lla r267135 : #i98601# add ImageScaleMode
2009-01-29 13:21:08 +0100 oj r267124 : #i98601# impl ScaleMode
2009-01-29 13:20:56 +0100 oj r267123 : #i98601# impl ScaleMode
2009-01-29 08:46:40 +0100 oj r267095 : new property: ScaleMode
2009-01-29 08:45:23 +0100 oj r267094 : new ScaleMode from UnControlImageModel
2009-01-29 08:28:12 +0100 oj r267093 : #i87930# close all sub forms/reports when the desktop is going to be terminated and no db frame exists
2009-01-28 19:54:34 +0100 lla r267082 : #i98557# pictures in report wizard
2009-01-28 15:06:25 +0100 oj r267060 : #i87930# close all sub forms/reports when the desktop is going to be terminated and no db frame exists
2009-01-28 11:38:41 +0100 lla r267046 : #i76783# handle binary fields in forms
2009-01-28 09:24:43 +0100 lla r267025 : #i10000#
2009-01-28 08:40:04 +0100 fs r267024 : #i10000#
2009-01-28 08:04:43 +0100 oj r267023 : #i93456# use resource strings for function names
2009-01-27 13:26:05 +0100 oj r266988 : check data field is type field or expression
2009-01-27 13:07:17 +0100 oj r266985 : check data field length
2009-01-27 11:48:19 +0100 oj r266974 : #i96823# return dll string as column name when no alias exists
2009-01-27 09:53:11 +0100 fs r266958 : display the message of a caught exception
2009-01-27 09:44:13 +0100 fs r266957 : #i58313# when retrieving all tables, just set an empty table type filter - the connection will care for translating this, by respecting the TableTypeFilterMode setting
2009-01-27 09:36:09 +0100 fs r266956 : #i58313# getTables: per JDBC spec, is not a valid table type filter. Translate it to 'null'.
2009-01-26 11:24:49 +0100 lla r266912 : #i97865# cleanups (AddField viewable in remote mode)
2009-01-26 07:49:27 +0100 lla r266897 : #i97865# AddField opens in remote case
2009-01-26 07:48:58 +0100 lla r266896 : #i97865# AddField opens in remote case
2009-01-26 07:48:42 +0100 lla r266895 : #i97865# AddField opens in remote case
2009-01-23 15:04:40 +0100 fs r266825 : consolidate the usage of OSQLMessageBox with MessageType==Warning into OSQLWarningBox
2009-01-23 10:47:33 +0100 fs r266787 : +supportsUserAdministration
2009-01-23 10:47:11 +0100 fs r266784 : use DatabaseMetaData.supportsUserAdministration
2009-01-23 07:55:59 +0100 lla r266767 : #i10000# fix gcc compiler failures
2009-01-21 15:08:55 +0100 lla r266673 : #i97265# Labels in HC (IsDark) with other color (viewable)
2009-01-19 14:58:54 +0100 lla r266504 : #i96523# last problems with FormatKey and '0' values fixed
2009-01-19 14:58:00 +0100 lla r266503 : #i96519# AddField help text
2009-01-19 11:59:02 +0100 fs r266485 : #i96523# for formatted field models, init them with TreatAsNumber = false
2009-01-16 10:31:49 +0100 lla r266405 : #i96793# add shrink to popup menu
2009-01-16 09:21:44 +0100 lla r266401 : #i96519# AddField contains a help text
2009-01-15 11:21:49 +0100 lla r266357 : #i96523# problem with XVclWindowPeer not fixed now
2009-01-15 09:19:20 +0100 lla r266335 : #i96523# more crashes fixed.
2009-01-14 13:08:34 +0100 lla r266291 : #i96523# problems with crashes fixed
2009-01-13 10:54:24 +0100 lla r266199 : #i96523# show datasource in formattedfields new files
2009-01-13 10:52:39 +0100 lla r266198 : #i96523# show datasource in formattedfields
2009-01-13 09:41:50 +0100 lla r266197 : #i96526# handling none existance default.otr
2009-01-12 12:55:49 +0100 fs r266151 : don't expect the control model to be a BoundComponent before adding as modify listener
2009-01-12 12:51:33 +0100 fs r266149 : #i88458# let the ImageControl be an XModifyBroadcaster, so the forms runtime can notice when the user changes the control content while it does not have the focus
2009-01-09 13:41:22 +0100 fs r266080 : doc
2009-01-09 13:14:14 +0100 fs r266077 : #i97377# SetModified when order is changed via DnD
2009-01-07 09:55:40 +0100 oj r265951 : merge from master
2009-01-07 09:55:24 +0100 oj r265950 : removed observer
2009-01-07 09:55:06 +0100 oj r265949 : merge from master
2009-01-07 07:29:11 +0100 oj r265945 : shadow var changed
2009-01-06 07:25:57 +0100 oj r265893 : CWS-TOOLING: rebase CWS dba32a to trunk@265758 (milestone: DEV300:m38)
2009-01-05 13:18:22 +0100 oj r265865 : convert to unix le
2009-01-05 09:13:52 +0100 lla r265857 : #i79423# lc_ sc_ permutation fix
2009-01-02 19:40:59 +0100 lla r265847 : #i79423# section shrink icons
2008-12-22 11:37:57 +0100 lla r265749 : #i97484# move component to negative Y-position
2008-12-22 11:37:05 +0100 lla r265748 : #i97484# move component to negative Y-position
2008-12-22 11:35:33 +0100 lla r265747 : #i97484# move component to negative Y-position
2008-12-22 11:25:07 +0100 lla r265745 : #i96757# changes via property browser was not undoable
2008-12-18 15:10:38 +0100 fs r265694 : corrected an condition in doFormListening, which otherwise leads to uncommitable grid columns in documents which are loaded from disc (not in documents which are newly created)
2008-12-18 14:54:39 +0100 fs r265692 : Hide Columns text slightly changed
2008-12-18 13:44:15 +0100 fs r265683 : #i94068# properly display erros happening during a form operation - at least once, and at most once
2008-12-18 11:28:29 +0100 fs r265677 : document the new InputRequired property
2008-12-18 11:04:15 +0100 fs r265676 : #i96530# createControlLabelPair: don't actually create a label for a checkbox
2008-12-18 10:35:53 +0100 fs r265674 : #i95226# when a column is replaced, and it's the selected column, update the selection
2008-12-18 10:34:42 +0100 fs r265673 : #i95226# refactoring of the implReplaced method
2008-12-18 10:34:28 +0100 fs r265672 : #i95226# when replacing a grid column, update the property browser
2008-12-18 10:33:17 +0100 fs r265671 : when an element is removed, remove it from m_aCurrentSelection, too (if necessary)
2008-12-18 10:31:57 +0100 fs r265670 : Hide Columns text slightly changed
2008-12-18 10:15:56 +0100 lla r265669 : #i14538# do not allow to press finish button twice
2008-12-18 08:56:33 +0100 lla r265665 : #i10000# build depend=t problem hacked.
2008-12-17 20:59:10 +0100 fs r265656 : #i89821# don't let a MultiLineEdit select all text when it receives the focus
2008-12-17 12:10:54 +0100 fs r265594 : #i97356#
2008-12-17 12:06:29 +0100 fs r265593 : #i97355# Print -> Printable
2008-12-17 11:59:31 +0100 fs r265591 : #i97350# combo boxes comment on list selection (as list boxes already do)
2008-12-16 09:53:57 +0100 lla r265527 : #i96526# handling none existance default.otr
2008-12-15 14:48:39 +0100 lla r265500 : #i79423# reparing, was wrong implemented
2008-12-12 15:08:33 +0100 lla r265424 : #i10000# remove wrong carridge returns
2008-12-12 15:07:55 +0100 lla r265423 : #i10000# remove wrong carridge returns
2008-12-12 15:06:41 +0100 lla r265422 : #i10000# remove wrong carridge returns
2008-12-12 10:23:13 +0100 lla r265395 : #i95234# reset DragDelta
2008-12-12 10:11:02 +0100 lla r265393 : #i79423# pre versions of shrink buttons
2008-12-11 15:32:13 +0100 fs r265318 : prevent a deadlock during complex.dbaccess.DatabaseDocument test
2008-12-11 15:30:06 +0100 fs r265316 : prevent a deadlock during complex.dbaccess.DatabaseDocument test
2008-12-11 15:07:05 +0100 fs r265307 : removed superfluous text
2008-12-11 12:29:54 +0100 lla r265282 : #i96757# cleanup second try
2008-12-11 12:09:15 +0100 lla r265278 : #i96757# cleanup
2008-12-11 12:07:56 +0100 lla r265277 : #i95234#
2008-12-10 14:04:39 +0100 lla r265183 : #i93472# D&D fixes
2008-12-10 12:29:33 +0100 lla r265168 : #i94067# add (APP|SYS)FONT to XUnitConversion
2008-12-10 12:15:02 +0100 lla r265166 : #i94067# add APPFONT, SYSFONT to MeasureUnit
2008-12-10 11:52:10 +0100 lla r265163 : #i94067# add comments
2008-12-06 20:33:05 +0100 fs r264935 : #i10000# precompiled header
2008-12-05 09:29:26 +0100 fs r264889 : #i10000#
2008-12-05 09:07:31 +0100 fs r264888 : #i10000#
2008-12-04 13:25:46 +0100 fs r264838 : CWS-TOOLING: rebase CWS dba32a to trunk@264807 (milestone: DEV300:m37)
2008-12-03 23:49:13 +0100 fs r264808 : merge changes from trunk, to be able to do a rebase
2008-12-03 17:13:09 +0100 lla r264801 : #i91041# update documentation
2008-12-03 16:57:04 +0100 lla r264799 : #i94067# allow convert(Point|Size)ToLogic as pixel also
2008-12-02 12:36:32 +0100 lla r264687 : #i96782# bring toolbar objects to menu structure
2008-12-02 10:32:44 +0100 lla r264667 : #i86255# make property work
2008-12-02 09:22:47 +0100 lla r264659 : #i79423# add section shrink toolbar
2008-12-02 07:41:22 +0100 lla r264657 : #i86255# add check box for Escape DateTime property
2008-12-02 07:37:17 +0100 lla r264656 : #i79423# new shrink buttons
2008-11-26 11:55:28 +0100 fs r264362 : #i96541#
FillPropertySet: do not only catch UnknownPropertyException when setting the Char/ParaAutoStyleName,
but also care for the other exceptions which can be thrown by XPropertySet::setPropertyValue.
This is actually not the real fix for #i96541#, but only a follow-up. The root cause of the issue
was fixed in CWS dba301b, but this here was another (potential) bug which popped up during investigations.
2008-11-25 09:04:40 +0100 lla r264273 : #i82083# new toolbox in GroupsSorting dialog
2008-11-25 08:56:08 +0100 lla r264272 : #i94729# change token strings into string list, move class out of function
2008-11-24 15:52:22 +0100 fs r264251 : #i96532# do not set AppendTableAlias, NameLengthLimit, etc., if the OXMLDataSourceInstance is used for elements at which those attributes never appear
2008-11-24 15:51:45 +0100 fs r264249 : #i96532# do not set AppendTableAlias, NameLengthLimit, etc., if the OXMLDataSourceInstance is used for elements at which those attributes never appear
2008-11-24 15:45:21 +0100 fs r264244 : #i96532# the API default for ParamNameSubst is false
2008-11-24 15:45:04 +0100 fs r264243 : #i96532# do not set AppendTableAlias, NameLengthLimit, etc., if the OXMLDataSourceInstance is used for elements at which those attributes never appear
2008-11-24 15:44:14 +0100 fs r264241 : #i96532# slight refactoring of exporting properties which have a XML default different from the API default
2008-11-24 10:50:01 +0100 lla r264216 : #i82083# icons for new toolbox
2008-11-24 09:38:45 +0100 lla r264205 : #i82083# new toolbox in GroupsSorting dialog
2008-11-24 09:32:20 +0100 lla r264201 : #i96501# cleanup assertions
2008-11-24 09:12:55 +0100 lla r264198 : #i83082# enhancement for toolboxes, better HC comfort
2008-11-24 08:46:43 +0100 lla r264197 : #i96501# fix problem with negative positions
2008-11-21 11:44:47 +0100 fs r264118 : #i57042# introduce a counter for suspending change notifications of a given property, so recursive calls are possible
2008-11-21 11:02:17 +0100 fs r264116 : #i96388# don't call ExecuteContextMenuAction when no action was chosen by the user
2008-11-21 10:36:53 +0100 fs r264114 : #i47384# assertion was wrong
2008-11-14 12:33:15 +0100 fs r263673 : #i47318# XRowSetChangeBroadcaster/Listener, to be able to listen for changes in an XRowSetSupplier's RowSet
2008-11-14 12:30:29 +0100 fs r263672 : #i47318# more refactoring
- BoundControlModels now listen at the XRowSetSupplier for changes in the supplied
RowSet, to properly revoke/register old/new listeners at the RowSet
- replaced ::osl::Mutex in various places with a ControlModelLock
2008-11-14 12:20:55 +0100 fs r263671 : when BUILD_TYPE includes QADEVOOO, the BUILD_QADEVOOO needs to bet set, too
2008-11-14 12:19:21 +0100 fs r263670 : oops, this was not intended to be committed
2008-11-12 11:08:10 +0100 fs r263579 : #i96096# new ctors taking UNO_QUERY_THROW
2008-11-12 09:15:54 +0100 fs r263576 : no need to load the complete dialog just to get a string which the dialog itself loads from resource
2008-11-10 17:55:45 +0100 fs r263535 : spelling in comment
2008-11-10 15:51:14 +0100 fs r263523 : #i47318# various refactorings
1. don't forward syntetic XLoadListener events from the grid control to
the grid columns. Instead, forward GridColumn::XChild::setParent to
the base class, which then can add itself as load listener
2. removed various occurances of XMultiServiceFactory, instead use the
::comphelper::ComponentContext
3. in O(Bound)ControlModel, have a mechanism to lock the instance (using
ControlModelLock) and fire property changes when the last lock dies.
2008-11-10 12:49:24 +0100 oj r263513 : #i94729# change token strings into string list
2008-11-10 12:13:15 +0100 oj r263512 : #i95222# export chart:title style as well
2008-11-10 08:55:25 +0100 oj r263507 : #i93471# show the correct tabpage when selecting a different object
2008-11-07 23:38:29 +0100 fs r263490 : #i95977# for the event input controls, add a component extending their functionality so they're reset when the users presses DEL
2008-11-07 23:35:39 +0100 fs r263489 : during #i95977#: When a VCL Window is deleted from within VCL code, the respective WindowPeer was never disposed. Corrected this.
2008-11-07 14:57:07 +0100 fs r263420 : #i95963# human-readable display names for event bindings
2008-11-06 10:34:52 +0100 fs r263366 : #i95865# don't use library names containing InvalidZipEntryFileNames - workaround until i95409 is fixed
2008-11-06 10:33:28 +0100 fs r263365 : #i95865#
copied the following change from CWS odfmetadata2 (not yet integrated) into CWS dba31d
- comphelper/inc/comphelper/storagehelper.hxx,
comphelper/source/misc/storagehelper.cxx:
+ add function IsValidZipEntryFileName (moved from module package)
2009-04-22 11:01:27 +00:00
|
|
|
{
|
|
|
|
if ( !getTypedControlWindow()->IsTravelSelect() )
|
|
|
|
// fire a commit
|
2015-10-09 15:17:24 +02:00
|
|
|
notifyModifiedValue();
|
CWS-TOOLING: integrate CWS dba32a
2009-04-16 13:08:19 +0200 oj r270882 : #i14538# set property at control
2009-04-16 13:04:28 +0200 oj r270881 : #i98557# remove binary string for SRB
2009-04-15 13:19:10 +0200 oj r270838 : #i96782# use type set at view
2009-04-14 14:53:20 +0200 oj r270778 : #i96782# set initialize size for custom shape
2009-04-06 14:19:14 +0200 oj r270546 : #i88432# correct pos when < 0 while resizing
2009-04-06 13:36:13 +0200 oj r270541 : #i96782# handle toolbar and menubar differently
2009-04-06 13:33:54 +0200 oj r270540 : #i96782# handle toolbar and menubar differently
2009-04-06 12:28:23 +0200 oj r270534 : #i96782# handle toolbar and menubar differently
2009-04-06 12:27:44 +0200 oj r270533 : #i96782# handle toolbar and menubar differently
2009-04-06 12:24:32 +0200 oj r270532 : #i96782# handle toolbar and menubar differently
2009-04-06 12:15:15 +0200 oj r270531 : do not initialze when field is empty
2009-04-06 10:06:08 +0200 oj r270528 : #i96782# clean up of menubar and remove duplicates
2009-04-06 09:47:49 +0200 oj r270527 : #i96519# adjust help text dynamic
2009-04-03 13:43:20 +0200 oj r270482 : do not need to remove section from observer they are already disposed
2009-04-03 13:27:28 +0200 fs r270479 : #i97356#
2009-04-02 11:30:39 +0200 fs r270386 : UNX line ends
2009-04-02 10:54:51 +0200 fs r270379 : UNX line ends
2009-04-02 10:39:57 +0200 fs r270378 : UNX line ends
2009-04-02 10:37:24 +0200 fs r270377 : why did this survive the rebase? was removed on trunk ...
2009-03-31 13:31:12 +0200 fs r270277 : component_foo should be public
2009-03-28 00:21:01 +0100 fs r270176 : manuallly merged the changes which happened in CWS before resync to m45, where the directory had been moved from reportdesign/registry to reportbuilder/registry
2009-03-27 23:01:20 +0100 fs r270174 : CWS-TOOLING: rebase CWS dba32a to trunk@270033 (milestone: DEV300:m45)
2009-03-11 12:23:35 +0100 fs r269310 : #i99958# ensure the ControlModelLock doesn't release twice
2009-03-06 09:07:32 +0100 fs r268970 : ignore output paths in SVN's status
2009-03-06 09:07:08 +0100 fs r268969 : ignore output paths in SVN's status
2009-03-04 11:28:02 +0100 oj r268800 : copy and paste error, check correct end now
2009-03-03 15:49:11 +0100 fs r268736 : #i10000# those merges were lost during the rebase (m38->m42)
2009-03-03 13:25:27 +0100 lla r268720 : #i99652# fix wrong refactoring
2009-02-27 11:12:56 +0100 fs r268566 : beautified
2009-02-27 10:53:47 +0100 fs r268561 : doFormListening(false) only when actually isFormListening() (found during complex test case XMLFormSettings with assertions)
2009-02-26 20:55:31 +0100 fs r268546 : #i96530# set the Label property of the bound control, if we didn't create a dedicated label control
2009-02-26 11:53:09 +0100 fs r268494 : #i10000#
2009-02-26 11:27:50 +0100 fs r268493 : #i10000#
2009-02-26 11:17:08 +0100 fs r268490 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN
2009-02-25 11:39:48 +0100 fs r268422 : #i10000# post-resync: INFO_ESCAPE_DATETIME got lost during rebase
2009-02-24 23:24:10 +0100 fs r268411 : CWS-TOOLING: rebase CWS dba32a to trunk@268395 (milestone: DEV300:m42)
2009-02-20 15:09:48 +0100 fs r268324 : respect ImplicitCatalog/SchemaRestriction in all necessary places
2009-02-20 13:48:10 +0100 oj r268318 : order of initialize corrected
2009-02-14 15:07:52 +0100 fs r267759 : #i98975# when an image does not have a bitmap, but a text, draw this (as placeholder)
2009-02-14 15:02:40 +0100 fs r267758 : consolidated and removed some duplicate code
2009-02-14 13:52:23 +0100 fs r267756 : #i10000#
2009-02-13 22:08:34 +0100 fs r267750 : #i100000#
2009-02-13 22:07:25 +0100 fs r267749 : #i10000#
2009-02-13 21:55:36 +0100 fs r267747 : #i10000#
2009-02-13 21:54:27 +0100 fs r267746 : use const_cast
2009-02-13 21:29:10 +0100 fs r267745 : #i10000#
2009-02-13 21:27:39 +0100 fs r267744 : #i10000#
2009-02-13 20:59:13 +0100 fs r267742 : #i10000#
2009-02-13 13:21:30 +0100 fs r267717 : better diagnostics
2009-02-13 13:17:24 +0100 fs r267715 : #i58313# support Catalog/SchemaRestriction settings, which are applied in getTables when 'all catalogs/schemas' are to be retrieved
2009-02-13 13:16:14 +0100 fs r267714 : filter out some more known global settings
2009-02-13 12:39:43 +0100 fs r267713 : #i58313# ImplicitCatalog/SchemaRestriction
2009-02-13 12:36:50 +0100 fs r267712 : when exporting data source settings, allow for properties which have a VOID default value, but are currently not VOID
2009-02-13 12:35:57 +0100 fs r267711 : implement XSet, to allow inserting properties which have a default value of VOID
2009-02-13 12:35:03 +0100 fs r267710 : +addVoidProperty
2009-02-13 10:20:08 +0100 fs r267697 : removed unused variable
2009-02-13 09:46:46 +0100 fs r267695 : refactored the table filtering code, to have a better base for introducing additional low level filters
2009-02-10 09:23:07 +0100 lla r267537 : #i10000# wrong line feed, double named variable
2009-02-09 12:13:08 +0100 oj r267508 : #i98605# notify hanlder
2009-02-09 11:50:34 +0100 oj r267507 : #i98926# solve refcount problem
2009-02-09 11:50:05 +0100 oj r267506 : #i98971# fix for simple html
2009-02-09 11:49:24 +0100 oj r267505 : #i98971# fix for simple html
2009-02-09 11:47:27 +0100 oj r267504 : invoke on copy
2009-02-09 09:51:00 +0100 fs r267500 : #i98316#
2009-02-09 09:46:10 +0100 fs r267499 : setCurrentSelection: don't reset the current form when we de-select everything
2009-02-09 09:43:45 +0100 fs r267498 : #i98316#
2009-02-08 21:25:18 +0100 fs r267496 : #i98272# introduce late ctor for cloning
2009-02-07 21:08:39 +0100 fs r267485 : #i98272# when copy-constructing a FmFormPageImpl, use the XCloneable of the forms collection, instead of XPersistObject (which is incompletely implemented)
2009-02-07 21:07:26 +0100 fs r267484 : removed obsolete include guards
2009-02-07 21:05:22 +0100 fs r267483 : #i98272# implement XCloneable
2009-02-06 15:02:48 +0100 lla r267467 : #i96523# add XImageControl
2009-02-06 14:41:38 +0100 oj r267463 : #i98926# late init when connection disposed but only when asked for
2009-02-06 13:49:57 +0100 lla r267457 : #i92860# bigint in forms doesn't allow input of values > 1, fixed
2009-02-06 13:03:55 +0100 oj r267455 : ImageScaleMode
2009-02-05 14:48:19 +0100 lla r267424 : #i89335# dropdown listboxes are 14 instead of 7 lines high
2009-02-05 13:40:00 +0100 oj r267423 : #i96945# insert new prop Opaque
2009-02-05 13:39:19 +0100 oj r267422 : #i96945# insert layer handling for hell and heaven
2009-02-05 13:29:32 +0100 lla r267420 : #i89335# add is null, is not null, is not like filter condition
2009-02-04 12:23:02 +0100 oj r267364 : #i98821# load table font settings
2009-02-04 10:05:27 +0100 oj r267351 : #i98821# load table font settings
2009-02-04 09:23:22 +0100 fs r267350 : checking persistency of UI settings in database documents - for the moment, capture table formattings (which is issue 98821)
2009-02-04 09:22:15 +0100 fs r267349 : moved some methods which are of wider interest from DatabaseDocument to FileHelper resp. TestCase
2009-02-04 08:56:27 +0100 oj r267347 : #i97586# UcbStreamHelper::CreateStream doesn't check all streamModes use different method
2009-02-04 08:23:26 +0100 oj r267346 : #i98701# check key size is >= 3 and some redesign
2009-02-03 23:29:24 +0100 fs r267345 : return the component (controller), not the frame
2009-02-03 23:28:53 +0100 fs r267344 : openExisting returns a controller now, not the frame (this was a bug)
2009-02-03 23:28:25 +0100 fs r267343 : openElement: properly return the component in the table/query case
2009-02-02 12:48:17 +0100 oj r267261 : #i96013# fix for relative path
2009-02-02 10:33:28 +0100 lla r267253 : #i98557# cleanups and consolidation
2009-02-02 09:37:23 +0100 lla r267250 : #i88432# resize will no longer move components to other sections
2009-02-02 09:08:24 +0100 oj r267245 : #i97475# write 0x1A at the end of the file
2009-01-30 19:39:20 +0100 lla r267230 : #i10000# unused parameters
2009-01-30 09:51:09 +0100 fs r267181 : onsolete
2009-01-30 09:49:27 +0100 fs r267180 : onsolete
2009-01-29 14:28:22 +0100 oj r267139 : #i96825# import cell style
2009-01-29 14:23:12 +0100 oj r267137 : #i98601# export imagescalehandler
2009-01-29 14:19:57 +0100 lla r267135 : #i98601# add ImageScaleMode
2009-01-29 13:21:08 +0100 oj r267124 : #i98601# impl ScaleMode
2009-01-29 13:20:56 +0100 oj r267123 : #i98601# impl ScaleMode
2009-01-29 08:46:40 +0100 oj r267095 : new property: ScaleMode
2009-01-29 08:45:23 +0100 oj r267094 : new ScaleMode from UnControlImageModel
2009-01-29 08:28:12 +0100 oj r267093 : #i87930# close all sub forms/reports when the desktop is going to be terminated and no db frame exists
2009-01-28 19:54:34 +0100 lla r267082 : #i98557# pictures in report wizard
2009-01-28 15:06:25 +0100 oj r267060 : #i87930# close all sub forms/reports when the desktop is going to be terminated and no db frame exists
2009-01-28 11:38:41 +0100 lla r267046 : #i76783# handle binary fields in forms
2009-01-28 09:24:43 +0100 lla r267025 : #i10000#
2009-01-28 08:40:04 +0100 fs r267024 : #i10000#
2009-01-28 08:04:43 +0100 oj r267023 : #i93456# use resource strings for function names
2009-01-27 13:26:05 +0100 oj r266988 : check data field is type field or expression
2009-01-27 13:07:17 +0100 oj r266985 : check data field length
2009-01-27 11:48:19 +0100 oj r266974 : #i96823# return dll string as column name when no alias exists
2009-01-27 09:53:11 +0100 fs r266958 : display the message of a caught exception
2009-01-27 09:44:13 +0100 fs r266957 : #i58313# when retrieving all tables, just set an empty table type filter - the connection will care for translating this, by respecting the TableTypeFilterMode setting
2009-01-27 09:36:09 +0100 fs r266956 : #i58313# getTables: per JDBC spec, is not a valid table type filter. Translate it to 'null'.
2009-01-26 11:24:49 +0100 lla r266912 : #i97865# cleanups (AddField viewable in remote mode)
2009-01-26 07:49:27 +0100 lla r266897 : #i97865# AddField opens in remote case
2009-01-26 07:48:58 +0100 lla r266896 : #i97865# AddField opens in remote case
2009-01-26 07:48:42 +0100 lla r266895 : #i97865# AddField opens in remote case
2009-01-23 15:04:40 +0100 fs r266825 : consolidate the usage of OSQLMessageBox with MessageType==Warning into OSQLWarningBox
2009-01-23 10:47:33 +0100 fs r266787 : +supportsUserAdministration
2009-01-23 10:47:11 +0100 fs r266784 : use DatabaseMetaData.supportsUserAdministration
2009-01-23 07:55:59 +0100 lla r266767 : #i10000# fix gcc compiler failures
2009-01-21 15:08:55 +0100 lla r266673 : #i97265# Labels in HC (IsDark) with other color (viewable)
2009-01-19 14:58:54 +0100 lla r266504 : #i96523# last problems with FormatKey and '0' values fixed
2009-01-19 14:58:00 +0100 lla r266503 : #i96519# AddField help text
2009-01-19 11:59:02 +0100 fs r266485 : #i96523# for formatted field models, init them with TreatAsNumber = false
2009-01-16 10:31:49 +0100 lla r266405 : #i96793# add shrink to popup menu
2009-01-16 09:21:44 +0100 lla r266401 : #i96519# AddField contains a help text
2009-01-15 11:21:49 +0100 lla r266357 : #i96523# problem with XVclWindowPeer not fixed now
2009-01-15 09:19:20 +0100 lla r266335 : #i96523# more crashes fixed.
2009-01-14 13:08:34 +0100 lla r266291 : #i96523# problems with crashes fixed
2009-01-13 10:54:24 +0100 lla r266199 : #i96523# show datasource in formattedfields new files
2009-01-13 10:52:39 +0100 lla r266198 : #i96523# show datasource in formattedfields
2009-01-13 09:41:50 +0100 lla r266197 : #i96526# handling none existance default.otr
2009-01-12 12:55:49 +0100 fs r266151 : don't expect the control model to be a BoundComponent before adding as modify listener
2009-01-12 12:51:33 +0100 fs r266149 : #i88458# let the ImageControl be an XModifyBroadcaster, so the forms runtime can notice when the user changes the control content while it does not have the focus
2009-01-09 13:41:22 +0100 fs r266080 : doc
2009-01-09 13:14:14 +0100 fs r266077 : #i97377# SetModified when order is changed via DnD
2009-01-07 09:55:40 +0100 oj r265951 : merge from master
2009-01-07 09:55:24 +0100 oj r265950 : removed observer
2009-01-07 09:55:06 +0100 oj r265949 : merge from master
2009-01-07 07:29:11 +0100 oj r265945 : shadow var changed
2009-01-06 07:25:57 +0100 oj r265893 : CWS-TOOLING: rebase CWS dba32a to trunk@265758 (milestone: DEV300:m38)
2009-01-05 13:18:22 +0100 oj r265865 : convert to unix le
2009-01-05 09:13:52 +0100 lla r265857 : #i79423# lc_ sc_ permutation fix
2009-01-02 19:40:59 +0100 lla r265847 : #i79423# section shrink icons
2008-12-22 11:37:57 +0100 lla r265749 : #i97484# move component to negative Y-position
2008-12-22 11:37:05 +0100 lla r265748 : #i97484# move component to negative Y-position
2008-12-22 11:35:33 +0100 lla r265747 : #i97484# move component to negative Y-position
2008-12-22 11:25:07 +0100 lla r265745 : #i96757# changes via property browser was not undoable
2008-12-18 15:10:38 +0100 fs r265694 : corrected an condition in doFormListening, which otherwise leads to uncommitable grid columns in documents which are loaded from disc (not in documents which are newly created)
2008-12-18 14:54:39 +0100 fs r265692 : Hide Columns text slightly changed
2008-12-18 13:44:15 +0100 fs r265683 : #i94068# properly display erros happening during a form operation - at least once, and at most once
2008-12-18 11:28:29 +0100 fs r265677 : document the new InputRequired property
2008-12-18 11:04:15 +0100 fs r265676 : #i96530# createControlLabelPair: don't actually create a label for a checkbox
2008-12-18 10:35:53 +0100 fs r265674 : #i95226# when a column is replaced, and it's the selected column, update the selection
2008-12-18 10:34:42 +0100 fs r265673 : #i95226# refactoring of the implReplaced method
2008-12-18 10:34:28 +0100 fs r265672 : #i95226# when replacing a grid column, update the property browser
2008-12-18 10:33:17 +0100 fs r265671 : when an element is removed, remove it from m_aCurrentSelection, too (if necessary)
2008-12-18 10:31:57 +0100 fs r265670 : Hide Columns text slightly changed
2008-12-18 10:15:56 +0100 lla r265669 : #i14538# do not allow to press finish button twice
2008-12-18 08:56:33 +0100 lla r265665 : #i10000# build depend=t problem hacked.
2008-12-17 20:59:10 +0100 fs r265656 : #i89821# don't let a MultiLineEdit select all text when it receives the focus
2008-12-17 12:10:54 +0100 fs r265594 : #i97356#
2008-12-17 12:06:29 +0100 fs r265593 : #i97355# Print -> Printable
2008-12-17 11:59:31 +0100 fs r265591 : #i97350# combo boxes comment on list selection (as list boxes already do)
2008-12-16 09:53:57 +0100 lla r265527 : #i96526# handling none existance default.otr
2008-12-15 14:48:39 +0100 lla r265500 : #i79423# reparing, was wrong implemented
2008-12-12 15:08:33 +0100 lla r265424 : #i10000# remove wrong carridge returns
2008-12-12 15:07:55 +0100 lla r265423 : #i10000# remove wrong carridge returns
2008-12-12 15:06:41 +0100 lla r265422 : #i10000# remove wrong carridge returns
2008-12-12 10:23:13 +0100 lla r265395 : #i95234# reset DragDelta
2008-12-12 10:11:02 +0100 lla r265393 : #i79423# pre versions of shrink buttons
2008-12-11 15:32:13 +0100 fs r265318 : prevent a deadlock during complex.dbaccess.DatabaseDocument test
2008-12-11 15:30:06 +0100 fs r265316 : prevent a deadlock during complex.dbaccess.DatabaseDocument test
2008-12-11 15:07:05 +0100 fs r265307 : removed superfluous text
2008-12-11 12:29:54 +0100 lla r265282 : #i96757# cleanup second try
2008-12-11 12:09:15 +0100 lla r265278 : #i96757# cleanup
2008-12-11 12:07:56 +0100 lla r265277 : #i95234#
2008-12-10 14:04:39 +0100 lla r265183 : #i93472# D&D fixes
2008-12-10 12:29:33 +0100 lla r265168 : #i94067# add (APP|SYS)FONT to XUnitConversion
2008-12-10 12:15:02 +0100 lla r265166 : #i94067# add APPFONT, SYSFONT to MeasureUnit
2008-12-10 11:52:10 +0100 lla r265163 : #i94067# add comments
2008-12-06 20:33:05 +0100 fs r264935 : #i10000# precompiled header
2008-12-05 09:29:26 +0100 fs r264889 : #i10000#
2008-12-05 09:07:31 +0100 fs r264888 : #i10000#
2008-12-04 13:25:46 +0100 fs r264838 : CWS-TOOLING: rebase CWS dba32a to trunk@264807 (milestone: DEV300:m37)
2008-12-03 23:49:13 +0100 fs r264808 : merge changes from trunk, to be able to do a rebase
2008-12-03 17:13:09 +0100 lla r264801 : #i91041# update documentation
2008-12-03 16:57:04 +0100 lla r264799 : #i94067# allow convert(Point|Size)ToLogic as pixel also
2008-12-02 12:36:32 +0100 lla r264687 : #i96782# bring toolbar objects to menu structure
2008-12-02 10:32:44 +0100 lla r264667 : #i86255# make property work
2008-12-02 09:22:47 +0100 lla r264659 : #i79423# add section shrink toolbar
2008-12-02 07:41:22 +0100 lla r264657 : #i86255# add check box for Escape DateTime property
2008-12-02 07:37:17 +0100 lla r264656 : #i79423# new shrink buttons
2008-11-26 11:55:28 +0100 fs r264362 : #i96541#
FillPropertySet: do not only catch UnknownPropertyException when setting the Char/ParaAutoStyleName,
but also care for the other exceptions which can be thrown by XPropertySet::setPropertyValue.
This is actually not the real fix for #i96541#, but only a follow-up. The root cause of the issue
was fixed in CWS dba301b, but this here was another (potential) bug which popped up during investigations.
2008-11-25 09:04:40 +0100 lla r264273 : #i82083# new toolbox in GroupsSorting dialog
2008-11-25 08:56:08 +0100 lla r264272 : #i94729# change token strings into string list, move class out of function
2008-11-24 15:52:22 +0100 fs r264251 : #i96532# do not set AppendTableAlias, NameLengthLimit, etc., if the OXMLDataSourceInstance is used for elements at which those attributes never appear
2008-11-24 15:51:45 +0100 fs r264249 : #i96532# do not set AppendTableAlias, NameLengthLimit, etc., if the OXMLDataSourceInstance is used for elements at which those attributes never appear
2008-11-24 15:45:21 +0100 fs r264244 : #i96532# the API default for ParamNameSubst is false
2008-11-24 15:45:04 +0100 fs r264243 : #i96532# do not set AppendTableAlias, NameLengthLimit, etc., if the OXMLDataSourceInstance is used for elements at which those attributes never appear
2008-11-24 15:44:14 +0100 fs r264241 : #i96532# slight refactoring of exporting properties which have a XML default different from the API default
2008-11-24 10:50:01 +0100 lla r264216 : #i82083# icons for new toolbox
2008-11-24 09:38:45 +0100 lla r264205 : #i82083# new toolbox in GroupsSorting dialog
2008-11-24 09:32:20 +0100 lla r264201 : #i96501# cleanup assertions
2008-11-24 09:12:55 +0100 lla r264198 : #i83082# enhancement for toolboxes, better HC comfort
2008-11-24 08:46:43 +0100 lla r264197 : #i96501# fix problem with negative positions
2008-11-21 11:44:47 +0100 fs r264118 : #i57042# introduce a counter for suspending change notifications of a given property, so recursive calls are possible
2008-11-21 11:02:17 +0100 fs r264116 : #i96388# don't call ExecuteContextMenuAction when no action was chosen by the user
2008-11-21 10:36:53 +0100 fs r264114 : #i47384# assertion was wrong
2008-11-14 12:33:15 +0100 fs r263673 : #i47318# XRowSetChangeBroadcaster/Listener, to be able to listen for changes in an XRowSetSupplier's RowSet
2008-11-14 12:30:29 +0100 fs r263672 : #i47318# more refactoring
- BoundControlModels now listen at the XRowSetSupplier for changes in the supplied
RowSet, to properly revoke/register old/new listeners at the RowSet
- replaced ::osl::Mutex in various places with a ControlModelLock
2008-11-14 12:20:55 +0100 fs r263671 : when BUILD_TYPE includes QADEVOOO, the BUILD_QADEVOOO needs to bet set, too
2008-11-14 12:19:21 +0100 fs r263670 : oops, this was not intended to be committed
2008-11-12 11:08:10 +0100 fs r263579 : #i96096# new ctors taking UNO_QUERY_THROW
2008-11-12 09:15:54 +0100 fs r263576 : no need to load the complete dialog just to get a string which the dialog itself loads from resource
2008-11-10 17:55:45 +0100 fs r263535 : spelling in comment
2008-11-10 15:51:14 +0100 fs r263523 : #i47318# various refactorings
1. don't forward syntetic XLoadListener events from the grid control to
the grid columns. Instead, forward GridColumn::XChild::setParent to
the base class, which then can add itself as load listener
2. removed various occurances of XMultiServiceFactory, instead use the
::comphelper::ComponentContext
3. in O(Bound)ControlModel, have a mechanism to lock the instance (using
ControlModelLock) and fire property changes when the last lock dies.
2008-11-10 12:49:24 +0100 oj r263513 : #i94729# change token strings into string list
2008-11-10 12:13:15 +0100 oj r263512 : #i95222# export chart:title style as well
2008-11-10 08:55:25 +0100 oj r263507 : #i93471# show the correct tabpage when selecting a different object
2008-11-07 23:38:29 +0100 fs r263490 : #i95977# for the event input controls, add a component extending their functionality so they're reset when the users presses DEL
2008-11-07 23:35:39 +0100 fs r263489 : during #i95977#: When a VCL Window is deleted from within VCL code, the respective WindowPeer was never disposed. Corrected this.
2008-11-07 14:57:07 +0100 fs r263420 : #i95963# human-readable display names for event bindings
2008-11-06 10:34:52 +0100 fs r263366 : #i95865# don't use library names containing InvalidZipEntryFileNames - workaround until i95409 is fixed
2008-11-06 10:33:28 +0100 fs r263365 : #i95865#
copied the following change from CWS odfmetadata2 (not yet integrated) into CWS dba31d
- comphelper/inc/comphelper/storagehelper.hxx,
comphelper/source/misc/storagehelper.cxx:
+ add function IsValidZipEntryFileName (moved from module package)
2009-04-22 11:01:27 +00:00
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
//= OMultilineFloatingEdit
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
class OMultilineFloatingEdit : public FloatingWindow
|
|
|
|
{
|
|
|
|
private:
|
2015-01-26 13:11:07 +02:00
|
|
|
VclPtr<MultiLineEdit> m_aImplEdit;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
|
|
|
protected:
|
2015-10-12 16:04:04 +02:00
|
|
|
virtual void Resize() override;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
|
|
|
public:
|
2015-10-18 07:53:51 +02:00
|
|
|
explicit OMultilineFloatingEdit(vcl::Window* _pParen);
|
2016-09-13 13:09:01 +02:00
|
|
|
virtual ~OMultilineFloatingEdit() override;
|
2015-10-12 16:04:04 +02:00
|
|
|
virtual void dispose() override;
|
2015-01-26 13:11:07 +02:00
|
|
|
MultiLineEdit& getEdit() { return *m_aImplEdit.get(); }
|
2001-01-12 10:35:45 +00:00
|
|
|
|
|
|
|
protected:
|
2015-10-12 16:04:04 +02:00
|
|
|
virtual bool PreNotify(NotifyEvent& _rNEvt) override;
|
2001-01-12 10:35:45 +00:00
|
|
|
};
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
OMultilineFloatingEdit::OMultilineFloatingEdit(vcl::Window* _pParent)
|
2001-01-12 10:35:45 +00:00
|
|
|
:FloatingWindow(_pParent, WB_BORDER)
|
2015-04-22 17:20:25 +01:00
|
|
|
,m_aImplEdit(VclPtr<MultiLineEdit>::Create(this, WB_VSCROLL|WB_IGNORETAB|WB_NOBORDER))
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2015-01-26 13:11:07 +02:00
|
|
|
m_aImplEdit->Show();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2015-01-26 13:11:07 +02:00
|
|
|
OMultilineFloatingEdit::~OMultilineFloatingEdit()
|
|
|
|
{
|
2015-03-10 09:07:06 +02:00
|
|
|
disposeOnce();
|
2015-01-26 13:11:07 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
void OMultilineFloatingEdit::dispose()
|
|
|
|
{
|
|
|
|
m_aImplEdit.disposeAndClear();
|
|
|
|
FloatingWindow::dispose();
|
|
|
|
}
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
void OMultilineFloatingEdit::Resize()
|
|
|
|
{
|
2015-01-26 13:11:07 +02:00
|
|
|
m_aImplEdit->SetSizePixel(GetOutputSizePixel());
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-01-18 00:18:52 +01:00
|
|
|
bool OMultilineFloatingEdit::PreNotify(NotifyEvent& _rNEvt)
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2015-09-25 13:06:09 +02:00
|
|
|
bool bResult = true;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-11-26 14:53:25 +00:00
|
|
|
MouseNotifyEvent nSwitch = _rNEvt.GetType();
|
|
|
|
if (MouseNotifyEvent::KEYINPUT == nSwitch)
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-08-23 22:22:32 +03:00
|
|
|
const vcl::KeyCode& aKeyCode = _rNEvt.GetKeyEvent()->GetKeyCode();
|
2001-01-12 10:35:45 +00:00
|
|
|
sal_uInt16 nKey = aKeyCode.GetCode();
|
|
|
|
|
|
|
|
if ( ( (KEY_RETURN == nKey)
|
|
|
|
&& !aKeyCode.IsShift()
|
|
|
|
)
|
|
|
|
|| ( (KEY_UP == nKey)
|
|
|
|
&& aKeyCode.IsMod2()
|
|
|
|
)
|
|
|
|
)
|
|
|
|
{
|
|
|
|
EndPopupMode();
|
|
|
|
}
|
|
|
|
else
|
2015-09-25 13:06:09 +02:00
|
|
|
bResult=FloatingWindow::PreNotify(_rNEvt);
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
else
|
2015-09-25 13:06:09 +02:00
|
|
|
bResult=FloatingWindow::PreNotify(_rNEvt);
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2015-09-25 13:06:09 +02:00
|
|
|
return bResult;
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
//= DropDownEditControl_Base
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
DropDownEditControl::DropDownEditControl( vcl::Window* _pParent, WinBits _nStyle )
|
2015-10-09 17:40:07 +02:00
|
|
|
:Edit( _pParent, _nStyle )
|
2015-11-10 10:14:53 +01:00
|
|
|
,m_pFloatingEdit( nullptr )
|
|
|
|
,m_pDropdownButton( nullptr )
|
2008-01-14 14:00:56 +00:00
|
|
|
,m_nOperationMode( eStringList )
|
2015-10-16 20:30:18 +01:00
|
|
|
,m_bDropdown(false)
|
|
|
|
,m_pHelper(nullptr)
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-02-21 12:53:51 +01:00
|
|
|
SetCompoundControl( true );
|
2006-01-03 15:20:54 +00:00
|
|
|
|
2015-04-22 17:20:25 +01:00
|
|
|
m_pImplEdit = VclPtr<MultiLineEdit>::Create( this, WB_TABSTOP | WB_IGNORETAB | WB_NOBORDER | (_nStyle & WB_READONLY) );
|
2015-01-07 10:42:07 +02:00
|
|
|
SetSubEdit( m_pImplEdit );
|
2001-01-12 10:35:45 +00:00
|
|
|
m_pImplEdit->Show();
|
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( _nStyle & WB_DROPDOWN )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2015-04-22 17:20:25 +01:00
|
|
|
m_pDropdownButton = VclPtr<PushButton>::Create( this, WB_NOLIGHTBORDER | WB_RECTSTYLE | WB_NOTABSTOP);
|
2014-10-14 09:36:33 +02:00
|
|
|
m_pDropdownButton->SetSymbol(SymbolType::SPIN_DOWN);
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
m_pDropdownButton->SetClickHdl( LINK( this, DropDownEditControl, DropDownHdl ) );
|
2001-01-12 10:35:45 +00:00
|
|
|
m_pDropdownButton->Show();
|
|
|
|
}
|
|
|
|
|
2015-04-22 17:20:25 +01:00
|
|
|
m_pFloatingEdit = VclPtr<OMultilineFloatingEdit>::Create(this);
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
m_pFloatingEdit->SetPopupModeEndHdl( LINK( this, DropDownEditControl, ReturnHdl ) );
|
2014-06-18 12:14:29 +02:00
|
|
|
m_pFloatingEdit->getEdit().SetReadOnly( ( _nStyle & WB_READONLY ) != 0 );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
2004-11-16 11:12:31 +00:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2015-10-09 15:17:24 +02:00
|
|
|
void DropDownEditControl::setControlHelper( CommonBehaviourControlHelper& _rControlHelper )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2015-10-09 17:40:07 +02:00
|
|
|
m_pHelper = &_rControlHelper;
|
2015-10-15 08:13:49 +02:00
|
|
|
m_pFloatingEdit->getEdit().SetModifyHdl( LINK( &_rControlHelper, CommonBehaviourControlHelper, EditModifiedHdl ) );
|
2015-10-09 15:17:24 +02:00
|
|
|
m_pImplEdit->SetGetFocusHdl( LINK( &_rControlHelper, CommonBehaviourControlHelper, GetFocusHdl ) );
|
2015-10-15 08:13:49 +02:00
|
|
|
m_pImplEdit->SetModifyHdl( LINK( &_rControlHelper, CommonBehaviourControlHelper, EditModifiedHdl ) );
|
2015-10-09 15:17:24 +02:00
|
|
|
m_pImplEdit->SetLoseFocusHdl( LINK( &_rControlHelper, CommonBehaviourControlHelper, LoseFocusHdl ) );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
DropDownEditControl::~DropDownEditControl()
|
2015-01-26 13:11:07 +02:00
|
|
|
{
|
2015-03-10 09:07:06 +02:00
|
|
|
disposeOnce();
|
2015-01-26 13:11:07 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
void DropDownEditControl::dispose()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2015-03-09 14:29:30 +02:00
|
|
|
SetSubEdit(nullptr);
|
2015-01-26 13:11:07 +02:00
|
|
|
m_pImplEdit.disposeAndClear();
|
2015-04-22 21:05:44 +01:00
|
|
|
m_pFloatingEdit.disposeAndClear();
|
|
|
|
m_pDropdownButton.disposeAndClear();
|
2015-10-09 17:40:07 +02:00
|
|
|
Edit::dispose();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
void DropDownEditControl::Resize()
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
::Size aOutSz = GetOutputSizePixel();
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2015-03-09 14:29:30 +02:00
|
|
|
if (m_pDropdownButton!=nullptr)
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
|
|
|
long nSBWidth = GetSettings().GetStyleSettings().GetScrollBarSize();
|
|
|
|
nSBWidth = CalcZoom( nSBWidth );
|
2012-08-24 12:34:22 +01:00
|
|
|
m_pImplEdit->setPosSizePixel( 0, 1, aOutSz.Width() - nSBWidth, aOutSz.Height()-2 );
|
|
|
|
m_pDropdownButton->setPosSizePixel( aOutSz.Width() - nSBWidth, 0, nSBWidth, aOutSz.Height() );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
else
|
2012-08-24 12:34:22 +01:00
|
|
|
m_pImplEdit->setPosSizePixel( 0, 1, aOutSz.Width(), aOutSz.Height()-2 );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-01-18 00:18:52 +01:00
|
|
|
bool DropDownEditControl::PreNotify( NotifyEvent& rNEvt )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2015-09-25 13:06:09 +02:00
|
|
|
bool bResult = true;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-11-26 14:53:25 +00:00
|
|
|
if (rNEvt.GetType() == MouseNotifyEvent::KEYINPUT)
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-08-23 22:22:32 +03:00
|
|
|
const vcl::KeyCode& aKeyCode = rNEvt.GetKeyEvent()->GetKeyCode();
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
sal_uInt16 nKey = aKeyCode.GetCode();
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( nKey == KEY_RETURN && !aKeyCode.IsShift() )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( m_pHelper )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2015-09-24 13:53:17 +02:00
|
|
|
m_pHelper->LoseFocusHdl( *m_pImplEdit.get() );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
m_pHelper->activateNextControl();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
}
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
else if ( nKey == KEY_DOWN && aKeyCode.IsMod2() )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
|
|
|
Invalidate();
|
2014-05-08 11:41:58 +02:00
|
|
|
ShowDropDown( true );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
else if ( KEYGROUP_CURSOR == aKeyCode.GetGroup()
|
|
|
|
|| nKey == KEY_HELP
|
|
|
|
|| KEYGROUP_FKEYS == aKeyCode.GetGroup()
|
|
|
|
|| m_nOperationMode == eMultiLineText
|
|
|
|
)
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2015-10-09 17:40:07 +02:00
|
|
|
bResult = Edit::PreNotify( rNEvt );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
else if ( m_nOperationMode == eStringList )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2005-01-21 16:26:37 +00:00
|
|
|
Selection aSel = m_pImplEdit->GetSelection();
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( aSel.Min() != aSel.Max() )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
aSel.Min() = FindPos( aSel.Min() );
|
|
|
|
aSel.Max() = FindPos( aSel.Max() );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
aSel.Min() = FindPos( aSel.Min() );
|
|
|
|
aSel.Max() = aSel.Min();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
Invalidate();
|
2014-05-08 11:41:58 +02:00
|
|
|
ShowDropDown( true );
|
2014-06-18 12:14:29 +02:00
|
|
|
m_pFloatingEdit->getEdit().GrabFocus();
|
|
|
|
m_pFloatingEdit->getEdit().SetSelection( aSel );
|
2014-09-23 11:20:40 +02:00
|
|
|
vcl::Window* pFocusWin = Application::GetFocusWindow();
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
pFocusWin->KeyInput( *rNEvt.GetKeyEvent() );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
else
|
2015-10-09 17:40:07 +02:00
|
|
|
bResult = Edit::PreNotify(rNEvt);
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2015-09-25 13:06:09 +02:00
|
|
|
return bResult;
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
namespace
|
|
|
|
{
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2013-09-19 15:20:39 +02:00
|
|
|
StlSyntaxSequence< OUString > lcl_convertMultiLineToList( const OUString& _rCompsedTextWithLineBreaks )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2013-10-28 13:20:52 +02:00
|
|
|
sal_Int32 nLines = comphelper::string::getTokenCount(_rCompsedTextWithLineBreaks, '\n');
|
2013-04-07 12:06:47 +02:00
|
|
|
StlSyntaxSequence< OUString > aStrings( nLines );
|
2018-08-12 23:07:44 +02:00
|
|
|
if (nLines)
|
|
|
|
{
|
|
|
|
StlSyntaxSequence< OUString >::iterator stringItem = aStrings.begin();
|
|
|
|
sal_Int32 nIdx {0};
|
|
|
|
do
|
|
|
|
{
|
|
|
|
*stringItem = _rCompsedTextWithLineBreaks.getToken( 0, '\n', nIdx );
|
|
|
|
++stringItem;
|
|
|
|
}
|
|
|
|
while (nIdx>0);
|
|
|
|
}
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
return aStrings;
|
|
|
|
}
|
|
|
|
|
2013-09-19 15:20:39 +02:00
|
|
|
OUString lcl_convertListToMultiLine( const StlSyntaxSequence< OUString >& _rStrings )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2018-07-28 18:01:28 +02:00
|
|
|
OUStringBuffer sMultiLineText;
|
2013-04-07 12:06:47 +02:00
|
|
|
for ( StlSyntaxSequence< OUString >::const_iterator item = _rStrings.begin();
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
item != _rStrings.end();
|
|
|
|
)
|
|
|
|
{
|
2018-07-28 18:01:28 +02:00
|
|
|
sMultiLineText.append(*item);
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( ++item != _rStrings.end() )
|
2018-07-28 18:01:28 +02:00
|
|
|
sMultiLineText.append("\n");
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
2018-07-28 18:01:28 +02:00
|
|
|
return sMultiLineText.makeStringAndClear();
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2013-09-19 15:20:39 +02:00
|
|
|
OUString lcl_convertListToDisplayText( const StlSyntaxSequence< OUString >& _rStrings )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2013-04-07 12:06:47 +02:00
|
|
|
OUStringBuffer aComposed;
|
|
|
|
for ( StlSyntaxSequence< OUString >::const_iterator strings = _rStrings.begin();
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
strings != _rStrings.end();
|
|
|
|
++strings
|
|
|
|
)
|
|
|
|
{
|
|
|
|
if ( strings != _rStrings.begin() )
|
2013-12-20 14:23:33 +02:00
|
|
|
aComposed.append( ';' );
|
|
|
|
aComposed.append( '\"' );
|
2007-05-10 09:50:15 +00:00
|
|
|
aComposed.append( *strings );
|
2013-12-20 14:23:33 +02:00
|
|
|
aComposed.append( '\"' );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
2007-05-10 09:50:15 +00:00
|
|
|
return aComposed.makeStringAndClear();
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
#define STD_HEIGHT 100
|
2016-01-11 11:54:13 +02:00
|
|
|
void DropDownEditControl::ShowDropDown( bool bShow )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
if (bShow)
|
|
|
|
{
|
|
|
|
::Point aMePos= GetPosPixel();
|
|
|
|
aMePos = GetParent()->OutputToScreenPixel( aMePos );
|
|
|
|
::Size aSize=GetSizePixel();
|
2017-03-30 20:27:55 +02:00
|
|
|
::tools::Rectangle aRect(aMePos,aSize);
|
2018-02-16 12:18:39 +02:00
|
|
|
aSize.setHeight( STD_HEIGHT );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
m_pFloatingEdit->SetOutputSizePixel(aSize);
|
2015-05-12 15:30:22 +02:00
|
|
|
m_pFloatingEdit->StartPopupMode( aRect, FloatWinPopupFlags::Down );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
|
|
|
|
m_pFloatingEdit->Show();
|
2014-06-18 12:14:29 +02:00
|
|
|
m_pFloatingEdit->getEdit().GrabFocus();
|
|
|
|
m_pFloatingEdit->getEdit().SetSelection(Selection(m_pFloatingEdit->getEdit().GetText().getLength()));
|
2014-05-08 11:41:58 +02:00
|
|
|
m_bDropdown = true;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( m_nOperationMode == eMultiLineText )
|
2014-06-18 12:14:29 +02:00
|
|
|
m_pFloatingEdit->getEdit().SetText( m_pImplEdit->GetText() );
|
2013-09-19 15:20:39 +02:00
|
|
|
m_pImplEdit->SetText("");
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
|
|
|
m_pFloatingEdit->Hide();
|
|
|
|
m_pFloatingEdit->Invalidate();
|
|
|
|
m_pFloatingEdit->Update();
|
|
|
|
|
|
|
|
// transfer the text from the floating edit to our own edit
|
2014-06-18 12:14:29 +02:00
|
|
|
OUString sDisplayText( m_pFloatingEdit->getEdit().GetText() );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( m_nOperationMode == eStringList )
|
|
|
|
sDisplayText = lcl_convertListToDisplayText( lcl_convertMultiLineToList( sDisplayText ) );
|
|
|
|
|
|
|
|
m_pImplEdit->SetText( sDisplayText );
|
2015-05-25 11:20:10 +02:00
|
|
|
GetParent()->Invalidate( InvalidateFlags::Children );
|
2014-05-08 11:41:58 +02:00
|
|
|
m_bDropdown = false;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
m_pImplEdit->GrabFocus();
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
long DropDownEditControl::FindPos(long nSinglePos)
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-06-18 12:14:29 +02:00
|
|
|
long nPos = 0;
|
2013-09-19 15:20:39 +02:00
|
|
|
OUString aOutput;
|
2014-06-18 12:14:29 +02:00
|
|
|
OUString aStr = m_pFloatingEdit->getEdit().GetText();
|
2013-09-19 15:20:39 +02:00
|
|
|
OUString aStr1 = GetText();
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2013-09-19 15:20:39 +02:00
|
|
|
if ((nSinglePos == 0) || (nSinglePos == aStr1.getLength()))
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
|
|
|
return nSinglePos;
|
|
|
|
}
|
|
|
|
|
2013-09-19 15:20:39 +02:00
|
|
|
if (!aStr.isEmpty())
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2011-09-10 08:11:19 +02:00
|
|
|
long nDiff=0;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2018-08-12 23:07:44 +02:00
|
|
|
sal_Int32 nIdx {0};
|
|
|
|
OUString aInput = aStr.getToken(0, '\n', nIdx );
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2013-09-19 15:20:39 +02:00
|
|
|
if (!aInput.isEmpty())
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2019-09-30 15:10:05 +02:00
|
|
|
aOutput += "\"" + aInput + "\"";
|
2001-01-12 10:35:45 +00:00
|
|
|
nDiff++;
|
|
|
|
}
|
|
|
|
|
2013-09-19 15:20:39 +02:00
|
|
|
if (nSinglePos <= aOutput.getLength())
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
|
|
|
nPos=nSinglePos-nDiff;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
2018-08-12 23:07:44 +02:00
|
|
|
while (nIdx>0)
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2018-08-12 23:07:44 +02:00
|
|
|
aInput=aStr.getToken(0, '\n', nIdx);
|
2013-09-19 15:20:39 +02:00
|
|
|
if (!aInput.isEmpty())
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2019-09-30 15:10:05 +02:00
|
|
|
aOutput += ";\"" + aInput + "\"";
|
2001-01-12 10:35:45 +00:00
|
|
|
nDiff += 2;
|
|
|
|
|
2013-09-19 15:20:39 +02:00
|
|
|
if (nSinglePos <= aOutput.getLength())
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
|
|
|
nPos=nSinglePos-nDiff;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return nPos;
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2016-10-05 07:56:12 +02:00
|
|
|
IMPL_LINK_NOARG( DropDownEditControl, ReturnHdl, FloatingWindow*, void)
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
2014-06-18 12:14:29 +02:00
|
|
|
OUString aStr = m_pFloatingEdit->getEdit().GetText();
|
2013-09-19 15:20:39 +02:00
|
|
|
OUString aStr2 = GetText();
|
2014-05-08 11:41:58 +02:00
|
|
|
ShowDropDown(false);
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if (aStr!=aStr2 || ( m_nOperationMode == eStringList ) )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( m_pHelper )
|
|
|
|
m_pHelper->notifyModifiedValue();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2016-10-05 07:56:12 +02:00
|
|
|
IMPL_LINK_NOARG( DropDownEditControl, DropDownHdl, Button*, void )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
|
|
|
ShowDropDown(!m_bDropdown);
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2013-04-07 12:06:47 +02:00
|
|
|
void DropDownEditControl::SetStringListValue( const StlSyntaxSequence< OUString >& _rStrings )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
SetText( lcl_convertListToDisplayText( _rStrings ) );
|
2014-06-18 12:14:29 +02:00
|
|
|
m_pFloatingEdit->getEdit().SetText( lcl_convertListToMultiLine( _rStrings ) );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2013-04-07 12:06:47 +02:00
|
|
|
StlSyntaxSequence< OUString > DropDownEditControl::GetStringListValue() const
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2014-06-18 12:14:29 +02:00
|
|
|
return lcl_convertMultiLineToList( m_pFloatingEdit->getEdit().GetText() );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2013-04-07 12:06:47 +02:00
|
|
|
void DropDownEditControl::SetTextValue( const OUString& _rText )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
2007-05-10 09:50:15 +00:00
|
|
|
OSL_PRECOND( m_nOperationMode == eMultiLineText, "DropDownEditControl::SetTextValue: illegal call!" );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
|
2014-06-18 12:14:29 +02:00
|
|
|
m_pFloatingEdit->getEdit().SetText( _rText );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
SetText( _rText );
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2013-04-07 12:06:47 +02:00
|
|
|
OUString DropDownEditControl::GetTextValue() const
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
OSL_PRECOND( m_nOperationMode == eMultiLineText, "DropDownEditControl::GetTextValue: illegal call!" );
|
|
|
|
return GetText();
|
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
//= OMultilineEditControl
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2014-09-23 11:20:40 +02:00
|
|
|
OMultilineEditControl::OMultilineEditControl( vcl::Window* pParent, MultiLineOperationMode _eMode, WinBits nWinStyle )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
:OMultilineEditControl_Base( _eMode == eMultiLineText ? PropertyControlType::MultiLineTextField : PropertyControlType::StringListField
|
|
|
|
, pParent
|
|
|
|
, ( nWinStyle | WB_DIALOGCONTROL ) & ( ~WB_READONLY | ~WB_DROPDOWN )
|
|
|
|
, false )
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
getTypedControlWindow()->setOperationMode( _eMode );
|
2015-10-09 17:40:07 +02:00
|
|
|
getTypedControlWindow()->setControlHelper( *this );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
void SAL_CALL OMultilineEditControl::setValue( const Any& _rValue )
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
impl_checkDisposed_throw();
|
|
|
|
|
|
|
|
switch ( getTypedControlWindow()->getOperationMode() )
|
|
|
|
{
|
|
|
|
case eMultiLineText:
|
|
|
|
{
|
2013-04-07 12:06:47 +02:00
|
|
|
OUString sText;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( !( _rValue >>= sText ) && _rValue.hasValue() )
|
|
|
|
throw IllegalTypeException();
|
|
|
|
getTypedControlWindow()->SetTextValue( sText );
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
break;
|
|
|
|
case eStringList:
|
|
|
|
{
|
2013-04-07 12:06:47 +02:00
|
|
|
Sequence< OUString > aStringLines;
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
if ( !( _rValue >>= aStringLines ) && _rValue.hasValue() )
|
|
|
|
throw IllegalTypeException();
|
2015-10-18 07:53:51 +02:00
|
|
|
getTypedControlWindow()->SetStringListValue( StlSyntaxSequence<OUString>(aStringLines) );
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
}
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Any SAL_CALL OMultilineEditControl::getValue()
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
impl_checkDisposed_throw();
|
|
|
|
|
|
|
|
Any aValue;
|
|
|
|
switch ( getTypedControlWindow()->getOperationMode() )
|
|
|
|
{
|
|
|
|
case eMultiLineText:
|
|
|
|
aValue <<= getTypedControlWindow()->GetTextValue();
|
|
|
|
break;
|
|
|
|
case eStringList:
|
|
|
|
aValue <<= getTypedControlWindow()->GetStringListValue();
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
return aValue;
|
|
|
|
}
|
|
|
|
|
2014-02-22 21:20:15 +01:00
|
|
|
|
2017-01-26 12:28:58 +01:00
|
|
|
Type SAL_CALL OMultilineEditControl::getValueType()
|
INTEGRATION: CWS pbrwuno (1.17.36); FILE MERGED
2006/02/13 07:28:41 fs 1.17.36.17: #i10000#
2006/02/10 11:51:46 fs 1.17.36.16: NullPointerException is unusual at addFooListener methods
2006/02/10 08:32:14 fs 1.17.36.15: RESYNC: (1.18-1.19); FILE MERGED
2005/12/20 10:54:54 fs 1.17.36.14: #i53095# new control type for editing hyperlinks
2005/12/19 12:23:15 fs 1.17.36.13: #i53095# don't produce an trailing empty line in multi line edits
2005/12/16 15:29:58 fs 1.17.36.12: ImplCalcLongValue: care for overflow
2005/10/26 14:03:33 fs 1.17.36.11: some cleanups for finalizing #i53095#
2005/10/24 08:42:07 fs 1.17.36.10: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:06 fs 1.17.36.9: #i53095# knitting some loose ends
2005/10/17 12:20:18 fs 1.17.36.8: make StringListField exchange a sequence< string >
2005/10/17 10:28:00 fs 1.17.36.7: #i53095# make numeric field exchange its values as double
2005/10/17 09:48:42 fs 1.17.36.6: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time
2005/10/17 07:17:05 fs 1.17.36.5: replace MeasurementUnit with css.util.MeasureUnit
2005/10/14 12:43:49 fs 1.17.36.4: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/05 07:10:42 fs 1.17.36.3: RESYNC: (1.17-1.18); FILE MERGED
2005/09/05 07:41:54 fs 1.17.36.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.17.36.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:32:54 +00:00
|
|
|
{
|
|
|
|
if ( getTypedControlWindow()->getOperationMode() == eMultiLineText )
|
2014-05-11 10:09:04 +02:00
|
|
|
return ::cppu::UnoType<OUString>::get();
|
2015-04-01 08:39:07 +02:00
|
|
|
return cppu::UnoType<Sequence< OUString >>::get();
|
2001-01-12 10:35:45 +00:00
|
|
|
}
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
} // namespace pcr
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2010-10-12 15:57:08 +02:00
|
|
|
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
|