Files
libreoffice/extensions/source/propctrlr/formcomponenthandler.cxx

3322 lines
134 KiB
C++
Raw Normal View History

/* -*- 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 .
*/
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
#include "controltype.hxx"
#include "pcrservices.hxx"
dba33a: summary migration from SVN 2009-11-06 13:10:39 +0000 msc r277387 : minor fix for automatic test 2009-11-06 13:09:33 +0000 msc r277385 : minor fix for automatic test 2009-11-06 12:30:57 +0000 fs r277383 : argh. On some virtual machines, waiting 5 seconds for the event to arrive is not enough. Increasing the timeout ... 2009-11-06 12:13:34 +0000 fs r277382 : this diagnostic code should not have slipped in 2009-11-05 13:21:06 +0000 fs r277369 : SHL2NOCHECK=TRUE (requested by hjs) 2009-11-04 14:09:46 +0000 msc r277355 : minor fix for automatic testing 2009-11-04 13:23:02 +0000 msc r277352 : minor fix for automatic testing 2009-11-04 10:53:28 +0000 msc r277341 : minor fix for automated testscript 2009-11-04 08:30:58 +0000 msc r277333 : minor fix for automatic test 2009-11-04 08:15:43 +0000 msc r277332 : minor fix for automatic test 2009-11-03 14:25:44 +0000 fs r277324 : #i10000# 2009-11-03 09:47:47 +0000 fs r277315 : found yet another help ID zombie ... moved formhelpid.hrc content to propctrlr.hrc, where it belongs 2009-11-03 08:50:24 +0000 fs r277312 : use createTempFileURL, which cares for some more specialities ... 2009-11-03 08:44:55 +0000 fs r277311 : when creating a temp file for purpose of getting a temp file URL, the delete the file immediately. On some machines/JVMs, the file exists, with write access denied, which isn't Good (TM) 2009-10-22 13:06:17 +0000 fs r277126 : removed wrong assertion 2009-10-21 08:10:35 +0000 fs r277077 : reverted the previous change, which was nonsense 2009-10-21 07:19:43 +0000 fs r277076 : export the component_foo functions, now that some of the objects are built with VISIBILITY_HIDDEN=TRUE 2009-10-21 07:08:35 +0000 fs r277075 : spare useless call 2009-10-20 21:26:31 +0000 fs r277072 : #i10000# 2009-10-20 08:06:04 +0000 fs r277039 : CWS-TOOLING: rebase CWS dba33a to trunk@277035 (milestone: DEV300:m62) 2009-10-16 09:55:25 +0000 fs r276960 : remove one of the superfluous implts_doLayout calls introduced with the previous patch 2009-10-15 13:18:52 +0000 fs r276941 : removed the basic tests. According to cn, they're not used anymore (for a long time), and according to 'du -h', they take up 6.0M on my hard disc. For too much for useless code, /me thinks. 2009-10-15 13:06:51 +0000 fs r276940 : #i10000# remove useless include (otherwise the compiler warning it provokes would need to be fixed by declaring VISIBILITY_HIDDEN=TRUE in the makefile.mk) 2009-10-15 12:52:39 +0000 fs r276939 : #i10000# 2009-10-15 12:44:26 +0000 fs r276938 : #i10000# 2009-10-15 12:00:33 +0000 fs r276936 : #i10000# 2009-10-15 10:31:37 +0000 fs r276934 : #i105259# prepare for the Hidden arg 2009-10-15 10:31:05 +0000 fs r276933 : IsMaximized -> const 2009-10-15 09:50:15 +0000 fs r276932 : during #i105259#: introduce an option to the layout manager to preserve, if possible, the size of the content window when layouting. Enable this option for embedded (SFX-based) documents opened for outplace editing. (the option is incompatible with in-place editing, anyway) This is because such embedded objects couple the (content) window size to the VisAreaSize, in that both are used interchangeably. When an embedded object is closed, it remembers the VisAreaSize, and restores it upon next open. This, however, leads to different content window sizes when the window is closed with another toolbar set than used during opening. This patch here prevents those different content window sizes. Also, now the content window size doesn't change when, explicitly or implicitly, a toolbar is shown or hidden. Instead, the content window size stays the same, and the container window size is adjusted. 2009-10-15 09:32:41 +0000 fs r276931 : during #i105259#: UNO access to more attributes of top windows 2009-10-15 09:30:28 +0000 fs r276930 : indention corrected (better readable) 2009-10-15 09:26:46 +0000 fs r276929 : during #i105259#: access to more attributes of top windows 2009-10-14 10:04:39 +0000 fs r276889 : connecting via services manager, not naming service 2009-10-12 11:31:08 +0000 fs r276831 : during #i105806# FillPropertySet: do not attempt to set *AutoStyleName if it doesn't exist 2009-10-12 11:24:44 +0000 fs r276830 : #i105806# getPropertyValue: throw an UnknownPropertyException for, well, unknown properties 2009-10-08 08:20:58 +0000 fs r276774 : implSubmit: re-throw WrappedTargetExceptions unmodified 2009-10-07 19:19:42 +0000 fs r276770 : #i105198# do not pass an CommandType if we do not have a command 2009-10-07 17:39:36 +0000 fs r276768 : export the OWeakObject::disposeWeakConnectionPoint symbol 2009-10-07 12:59:17 +0000 fs r276754 : #i87693# 2009-10-07 11:19:22 +0000 fs r276752 : #i10000# 2009-10-07 10:21:08 +0000 fs r276748 : #105482# do not require a controller, at least not in *all* circumstances (executed reports have a model, the ReportDefinition, but no Controller) 2009-10-07 10:04:08 +0000 fs r276747 : copying the changes from CWS fwk121 herein, in particular the fix for issue #i105371# 2009-10-07 09:58:30 +0000 fs r276746 : copying the changes from CWS fwk121 herein, in particular the fix for issue #i105371# 2009-10-07 09:48:14 +0000 fs r276744 : removed (now) pointless assertion 2009-10-07 06:59:19 +0000 fs r276740 : export the OWeakObject::disposeWeakConnectionPoint symbol 2009-10-07 06:44:43 +0000 fs r276739 : OComponentHelper::release & WeakAggComponentImplHelperBase::release: when our ref count drops to 0, call OWeakObject's disposeWeakConnectionPoint before (temporarily) incrementing the ref count, again. This ensures that our adapter cannot create references to the dying object anymore. (A complex test case in dbaccess (#i105505#) triggered such a situation, but in another class using an analogous release/dispose/destroy pattern, namely WeakComponentImplHelperBase) 2009-10-07 06:37:20 +0000 fs r276738 : found during some new complex test cases: call disposeWeakConnectionPoint before actually starting to destroy the object, this ensures no other threads will resurrect it while it is dying 2009-10-06 21:58:24 +0000 fs r276734 : oops, two small corrections to the previous fix (hey, complex test cases are cool) 2009-10-06 21:51:16 +0000 fs r276733 : log the name of the data source which cannot be revoked 2009-10-06 21:50:41 +0000 fs r276732 : more detailed error message when cleanup fails 2009-10-06 21:50:01 +0000 fs r276731 : reworked the ModelImpl caching. The new and improved UNO API test for css.sdb.RowSet revealed some inconsistencies, in whether the objects are cached by their URL, or by their registration name. This has been changed to caching by registration name. 2009-10-06 13:50:34 +0000 fs r276714 : print diagnostics when we cannot clean up the test case 2009-10-06 13:45:02 +0000 fs r276713 : this test failed all the time, since the core (rightfully) threw an exception. Disabled it for the moment, until issue 84253 is fixed 2009-10-06 12:52:46 +0000 fs r276711 : rewrote this test. Now we do not re-use the same .odb across different test cases, as this leads to unreliable (timing-dependent) results/failures. Instead, every test sets up a new odb file. Also, did some re-factoring, improved the cleanup code, and caught a few more errors. 2009-10-06 12:51:07 +0000 fs r276710 : DBTools taking a logger now 2009-10-06 12:50:42 +0000 fs r276709 : taking a PrintWriter for logging purpose 2009-10-06 12:50:03 +0000 fs r276708 : DBTools taking a logger now 2009-10-06 12:49:22 +0000 fs r276707 : typo 2009-10-06 12:49:03 +0000 fs r276706 : typo 2009-10-06 12:48:52 +0000 fs r276705 : wrappers around some database-related services - initial versions only, to evolve over time, and intended to finally replace the DBTools class 2009-10-06 12:48:02 +0000 fs r276704 : typo 2009-10-06 12:38:42 +0000 fs r276702 : some better diagnostics, done during getting the API tests to work more reliably 2009-10-06 10:35:51 +0000 fs r276698 : when living in, e.g., the DataSourceBrowser, we can't expect to find an XModifiable2, so don't assert its existence 2009-10-05 12:47:52 +0000 oj r276677 : #i105607# check for read moved into if scope 2009-10-05 11:37:06 +0000 fs r276676 : when saving a file fails, retrieve the error message from the InteractionRequestStringResolver - this is better than any generic message we can create 2009-10-05 10:04:23 +0000 oj r276673 : #i105607# check for read moved into if scope 2009-10-05 09:46:17 +0000 fs r276671 : #i10000# 2009-10-05 08:43:58 +0000 fs r276664 : #i105505# release: dispose the (base classes) weak connection point before disposing ourself, and in particular before temporarily incrementing our ref count, again. This way, we prevent that a separate thread re-surrects us (using the weak connection point's queryAdapted) while we're in the process of destruction 2009-10-05 08:41:49 +0000 fs r276663 : #i105505# +disposeWeakConnectionPoint (outsourced into dedicated method from ::release) 2009-10-05 08:40:26 +0000 fs r276662 : no need to derived from OSubComponent, its features are not used, directly derive from WeakComponentImplFoo instead 2009-10-05 08:39:38 +0000 fs r276661 : #i105505# diagnostics 2009-10-05 08:39:16 +0000 fs r276660 : #i105505# +testDocumentRevenants 2009-10-05 08:36:01 +0000 fs r276659 : #i105560# reverted the removal of GenericController::openHelpAgent - this is needed in module reportdesign 2009-10-04 19:53:30 +0000 fs r276657 : #105560# remove unused code thanks to cmc@openoffice.org for submitting the patch 2009-10-04 19:50:28 +0000 fs r276656 : #i105550# remove unused 'fire' method (thanks to cmc) 2009-10-03 16:13:15 +0000 fs r276655 : CWS-TOOLING: rebase CWS dba33a to trunk@276429 (milestone: DEV300:m60) 2009-10-02 19:20:48 +0000 fs r276651 : #i104117# lotta changed IDs ... 2009-10-02 10:52:24 +0000 fs r276634 : #i105505# If a model is created, and is a revenant of a previous incarnation, then ensure it is properly initialized. In particular, in its ctor, set the state to "Initializing", not "Initialized", and then let the ModelImpl call attachResource. This ensures that the model is initialized completely, including firing the necessary events. 2009-10-02 10:51:08 +0000 fs r276633 : #i105505# always do an attachResource at the newly loaded model, even if it (internally) was not really loaded, but only a revenant of a previous incarnation of this document 2009-10-01 11:10:13 +0000 fs r276597 : do not rely on the name 'Standard' for the one and only form in a document 2009-10-01 10:36:29 +0000 fs r276590 : #i105509# don't rely on default form component names, use indexes 2009-10-01 09:12:20 +0000 fs r276582 : #i105505# 2009-09-30 07:55:21 +0000 fs r276542 : removed some unsed methods / spared some unnecessary pixel<->logic conversion 2009-09-30 07:53:22 +0000 fs r276541 : removed unneeded methods 2009-09-30 06:35:59 +0000 fs r276538 : #i10000# 2009-09-29 13:45:02 +0000 fs r276531 : refactored the Roadmap* classes, to be able to fix above-mentioned #i105113# 2009-09-29 10:27:10 +0000 fs r276520 : #i105367# 2009-09-29 08:46:45 +0000 fs r276510 : #i104956# cleaned up the makefiles 2009-09-28 21:00:07 +0000 fs r276505 : #i104117# sourced those IDs out from extension.hrc 2009-09-28 20:59:05 +0000 fs r276504 : no need to let one FREE... 2009-09-28 20:53:36 +0000 fs r276503 : #i104117# cleaned up the mess with help IDs in module extensions. Formerly, extensions used to use help IDs which were declared in module svx, and vice versa. Also, help ID ranges were not respected. 2009-09-28 11:25:36 +0000 fs r276489 : typo 2009-09-28 11:25:10 +0000 fs r276488 : #i105235# 2009-09-24 11:53:16 +0000 fs r276423 : #i105234# do not zoom the control when they view information is still uninitialized (happens at least in Writer when opening a form document) 2009-09-24 09:42:28 +0000 fs r276415 : #i105234# proper zoom handling for the nav bar 2009-09-24 09:42:19 +0000 fs r276414 : #i105234# setZoom: care for precision errors caused by implicit conversion float->double 2009-09-16 11:11:43 +0000 fs r276195 : #i105082# consolidated the sub storage handling, by delegating more functionality into the DocumentStorageAccess class. As a result, there won't be that many unnecessary commits anymore. Also, the two different storage caches (in ModelImpl::m_aStorages and DocumentStorageAccess::m_aExposedStorages) have been consolidated. This is not really part of the fix of issue 105082, but it helped reducing the calls to the storage/package implementation. 2009-09-15 21:42:27 +0000 fs r276190 : don't calculate space for BOLD if the text is not really bold (speeds up rendering for large tree structures) 2009-09-15 20:20:23 +0000 fs r276188 : getTypeInfo: fill m_aTypeInfoRows only if really all type infos could be retrieved 2009-09-15 20:19:29 +0000 fs r276187 : do not continue loading when the controller initialization throws an error 2009-09-14 12:25:57 +0000 fs r276119 : oops, this patch was not intended for this CWS 2009-09-14 12:13:57 +0000 fs r276114 : #cr6875455# introduce a ReferenceDevice property for various control models 2009-09-14 10:33:02 +0000 fs r276106 : removed dead file 2009-09-09 08:37:31 +0000 fs r275972 : remove OSL_TRACE in VCLXButton dtor 2009-09-08 11:19:17 +0000 oj r275926 : i76534# remove mnemonic from fixed text 2009-09-07 08:39:37 +0000 fs r275874 : create CWS dba33a from cws/dba32g@275857 (CWS: dba32g)
2009-11-27 12:39:32 +00:00
#include "propctrlr.hrc"
2010-01-07 09:15:49 +01:00
#include "extensio.hrc"
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
#include "fontdialog.hxx"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include "formcomponenthandler.hxx"
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
#include "formlinkdialog.hxx"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include "formmetadata.hxx"
#include "formresid.hrc"
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
#include "formstrings.hxx"
#include "handlerhelper.hxx"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include "listselectiondlg.hxx"
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
#include "pcrcommon.hxx"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include "selectlabeldialog.hxx"
#include "taborder.hxx"
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
#include "usercontrol.hxx"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include <com/sun/star/lang/NullPointerException.hpp>
#include <com/sun/star/awt/XControlModel.hpp>
#include <com/sun/star/lang/XServiceInfo.hpp>
#include <com/sun/star/form/FormComponentType.hpp>
#include <com/sun/star/beans/PropertyAttribute.hpp>
#include <com/sun/star/util/XNumberFormatsSupplier.hpp>
#include <com/sun/star/container/XNameAccess.hpp>
#include <com/sun/star/form/XForm.hpp>
#include <com/sun/star/container/XChild.hpp>
#include <com/sun/star/sdb/OrderDialog.hpp>
#include <com/sun/star/sdb/FilterDialog.hpp>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include <com/sun/star/sdbc/XConnection.hpp>
#include <com/sun/star/sdb/CommandType.hpp>
#include <com/sun/star/sdb/DatabaseContext.hpp>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include <com/sun/star/form/XGridColumnFactory.hpp>
#include <com/sun/star/sdb/SQLContext.hpp>
#include <com/sun/star/sdbcx/XTablesSupplier.hpp>
#include <com/sun/star/sdb/XQueriesSupplier.hpp>
#include <com/sun/star/form/ListSourceType.hpp>
#include <com/sun/star/ui/dialogs/XExecutableDialog.hpp>
#include <com/sun/star/sdb/XSingleSelectQueryComposer.hpp>
#include <com/sun/star/ui/dialogs/XFilePickerControlAccess.hpp>
#include <com/sun/star/ui/dialogs/TemplateDescription.hpp>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include <com/sun/star/ui/dialogs/ExtendedFilePickerElementIds.hpp>
#include <com/sun/star/awt/XTabControllerModel.hpp>
#include <com/sun/star/form/FormSubmitEncoding.hpp>
#include <com/sun/star/awt/VisualEffect.hpp>
#include <com/sun/star/form/FormButtonType.hpp>
#include <com/sun/star/inspection/PropertyControlType.hpp>
#include <com/sun/star/util/MeasureUnit.hpp>
#include <com/sun/star/inspection/XObjectInspectorUI.hpp>
#include <com/sun/star/inspection/PropertyLineElement.hpp>
#include <com/sun/star/resource/XStringResourceManager.hpp>
#include <com/sun/star/resource/MissingResourceException.hpp>
#include <com/sun/star/report/XReportDefinition.hpp>
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
#include <com/sun/star/graphic/GraphicObject.hpp>
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
#include <com/sun/star/text/WritingMode2.hpp>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include <comphelper/extract.hxx>
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
#include <connectivity/dbconversion.hxx>
#include <connectivity/dbexception.hxx>
#include <cppuhelper/exc_hlp.hxx>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include <sfx2/app.hxx>
#include <sfx2/basedlgs.hxx>
#include <sfx2/docfilt.hxx>
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
#include <sfx2/filedlghelper.hxx>
#include <svl/ctloptions.hxx>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include <svtools/colrdlg.hxx>
#include <svl/filenotation.hxx>
#include <svl/intitem.hxx>
#include <svl/itemset.hxx>
#include <unotools/moduleoptions.hxx>
#include <svl/numuno.hxx>
#include <svl/urihelper.hxx>
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
#include <svx/dialogs.hrc>
#include <svx/numinf.hxx>
#include <svx/svxdlg.hxx>
#include <svx/svxids.hrc>
#include <toolkit/helper/vclunohelper.hxx>
#include <tools/diagnose_ex.h>
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
#include <vcl/msgbox.hxx>
#include <vcl/stdtext.hxx>
#include <vcl/wrkwin.hxx>
CWS-TOOLING: integrate CWS dba31f 2008-12-10 14:16:09 +0100 oj r265185 : #i96658# remove is 2008-12-10 08:46:07 +0100 oj r265147 : remove duplicate ids 2008-12-10 08:35:02 +0100 oj r265146 : #i96658# remove is 2008-12-09 11:44:35 +0100 oj r265072 : use of tools::StringresourceList 2008-12-09 11:43:41 +0100 oj r265071 : new class to read string elements from a Resource 2008-12-09 11:41:56 +0100 oj r265070 : export StringListResource 2008-12-09 11:38:17 +0100 oj r265068 : change string ; to more string objects 2008-12-08 12:11:43 +0100 oj r264985 : change default-license-id to lic-en-US 2008-12-05 12:06:09 +0100 oj r264896 : disable check to uncheck 2008-12-04 08:58:50 +0100 oj r264814 : #i96517,i96520,i96522# d&d, background, state fixed 2008-12-04 08:53:29 +0100 oj r264813 : #i96434# use document ui name from filter 2008-12-04 08:41:06 +0100 oj r264812 : #i96434# use document ui name from filter 2008-12-02 13:48:49 +0100 lla r264697 : #i96526# extra string for default otr wasn't found 2008-11-28 11:46:31 +0100 oj r264536 : move toolbar and resize add field dlg 2008-11-28 08:38:22 +0100 oj r264526 : load string resources 2008-11-27 19:28:52 +0100 oj r264520 : unsigned 2008-11-27 19:10:19 +0100 oj r264517 : move class into unnamed namespace 2008-11-27 18:33:38 +0100 oj r264514 : wrong param 2008-11-27 16:52:39 +0100 oj r264510 : #i96622# wrong string replacement 2008-11-27 16:46:03 +0100 oj r264509 : remove unused var 2008-11-27 13:37:16 +0100 oj r264484 : #i96432# notify only when not in special mode of the page 2008-11-27 13:16:47 +0100 oj r264479 : #i95224# accept alias in group by 2008-11-27 12:35:19 +0100 oj r264477 : #i95416# always show localized strings in the start marker 2008-11-27 09:49:29 +0100 oj r264455 : #i93460# set split pos 2008-11-27 09:05:27 +0100 oj r264447 : #i96453# use extension from mimetype / mediatype 2008-11-26 16:24:43 +0100 oj r264416 : #i96520# #i96522# #i96519# some changes at the add field dialog 2008-11-26 16:20:27 +0100 oj r264414 : #i93420# prevent to register a none system file url 2008-11-26 16:19:02 +0100 oj r264413 : #i96522# new class to paste multiple objects 2008-11-26 10:06:12 +0100 oj r264349 : #i96191# introduce new error message and check if type was defined aand should not be changed 2008-11-26 10:06:12 +0100 oj r264348 : #i96191# throw error when decimal is to big 2008-11-25 12:08:59 +0100 oj r264281 : #i96431# correct state for align and move 2008-11-25 11:54:47 +0100 oj r264280 : #i96428# when new bind to first table 2008-11-25 11:49:55 +0100 oj r264279 : #i96434# add report output format to inspection 2008-11-25 11:49:05 +0100 oj r264278 : #i96434# add report output format to inspection 2008-11-24 10:46:23 +0100 oj r264215 : #i96458# size width for controls 2008-11-24 09:28:56 +0100 oj r264199 : #i96459# mark detail section when nothing is selected 2008-11-20 12:02:35 +0100 oj r264038 : #i96191# fix check for prec 2008-11-20 08:06:32 +0100 oj r264026 : #i90949# patch MID function 2008-11-11 13:14:58 +0100 oj r263555 : #i96086# apply patch 2008-11-11 11:34:46 +0100 oj r263549 : #i94128# correct height of section when controls moved outside 2008-11-11 07:52:08 +0100 oj r263544 : #i94729# fix string with ; as sep 2008-11-11 07:45:27 +0100 oj r263543 : #i95222# export chart title style 2008-11-11 07:43:37 +0100 oj r263542 : #i92541# fix line height
2008-12-10 13:41:25 +00:00
#include <tools/StringListResource.hxx>
2010-10-15 18:15:35 +01:00
#include <sal/macros.h>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
#include <limits>
#include <memory>
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
#define GRAPHOBJ_URLPREFIX "vnd.sun.star.GraphicObject:"
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
extern "C" void SAL_CALL createRegistryInfo_FormComponentPropertyHandler()
{
::pcr::FormComponentPropertyHandler::registerImplementation();
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
namespace pcr
{
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
using namespace ::com::sun::star;
using namespace uno;
using namespace lang;
using namespace beans;
using namespace frame;
using namespace script;
using namespace form;
using namespace util;
using namespace awt;
using namespace sdb;
using namespace sdbc;
using namespace sdbcx;
using namespace report;
using namespace container;
using namespace ui::dialogs;
using namespace inspection;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
using namespace ::dbtools;
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
namespace WritingMode2 = ::com::sun::star::text::WritingMode2;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
//= FormComponentPropertyHandler
#define PROPERTY_ID_ROWSET 1
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
FormComponentPropertyHandler::FormComponentPropertyHandler( const Reference< XComponentContext >& _rxContext )
:FormComponentPropertyHandler_Base( _rxContext )
,::comphelper::OPropertyContainer(FormComponentPropertyHandler_Base::rBHelper)
,m_sDefaultValueString( PcrRes(RID_STR_STANDARD).toString() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
,m_eComponentClass( eUnknown )
,m_bComponentIsSubForm( false )
,m_bHaveListSource( false )
,m_bHaveCommand( false )
,m_nClassId( 0 )
{
registerProperty(PROPERTY_ROWSET,PROPERTY_ID_ROWSET,0,&m_xRowSet,cppu::UnoType<decltype(m_xRowSet)>::get());
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
FormComponentPropertyHandler::~FormComponentPropertyHandler()
{
}
IMPLEMENT_FORWARD_XINTERFACE2(FormComponentPropertyHandler,FormComponentPropertyHandler_Base,::comphelper::OPropertyContainer)
OUString SAL_CALL FormComponentPropertyHandler::getImplementationName_static( ) throw (RuntimeException)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
return OUString( "com.sun.star.comp.extensions.FormComponentPropertyHandler" );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
Sequence< OUString > SAL_CALL FormComponentPropertyHandler::getSupportedServiceNames_static( ) throw (RuntimeException)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
Sequence<OUString> aSupported { "com.sun.star.form.inspection.FormComponentPropertyHandler" };
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
return aSupported;
}
// TODO: -> export from toolkit
struct LanguageDependentProp
{
const char* pPropName;
sal_Int32 nPropNameLength;
};
static const LanguageDependentProp aLanguageDependentProp[] =
{
{ "Text", 4 },
{ "Label", 5 },
{ "Title", 5 },
{ "HelpText", 8 },
{ "CurrencySymbol", 14 },
{ "StringItemList", 14 },
{ nullptr, 0 }
};
namespace
{
bool lcl_isLanguageDependentProperty( const OUString& aName )
{
bool bRet = false;
const LanguageDependentProp* pLangDepProp = aLanguageDependentProp;
while( pLangDepProp->pPropName != nullptr )
{
if( aName.equalsAsciiL( pLangDepProp->pPropName, pLangDepProp->nPropNameLength ))
{
bRet = true;
break;
}
pLangDepProp++;
}
return bRet;
}
Reference< resource::XStringResourceResolver > lcl_getStringResourceResolverForProperty
( const Reference< XPropertySet >& _xComponent, const OUString& _rPropertyName,
const Any& _rPropertyValue )
{
Reference< resource::XStringResourceResolver > xRet;
const TypeClass eType = _rPropertyValue.getValueType().getTypeClass();
if ( (eType == TypeClass_STRING || eType == TypeClass_SEQUENCE) &&
lcl_isLanguageDependentProperty( _rPropertyName ) )
{
static const char s_sResourceResolverPropName[] = "ResourceResolver";
Reference< resource::XStringResourceResolver > xStringResourceResolver;
try
{
xStringResourceResolver.set( _xComponent->getPropertyValue( s_sResourceResolverPropName ),UNO_QUERY);
if( xStringResourceResolver.is() &&
xStringResourceResolver->getLocales().getLength() > 0 )
{
xRet = xStringResourceResolver;
}
}
2011-12-10 22:14:57 +09:00
catch(const UnknownPropertyException&)
{
// nii
}
}
return xRet;
}
}
Any FormComponentPropertyHandler::impl_getPropertyValue_throw( const OUString& _rPropertyName ) const
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
const PropertyId nPropId( impl_getPropertyId_throwUnknownProperty( _rPropertyName ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Any aPropertyValue( m_xComponent->getPropertyValue( _rPropertyName ) );
Reference< resource::XStringResourceResolver > xStringResourceResolver
= lcl_getStringResourceResolverForProperty( m_xComponent, _rPropertyName, aPropertyValue );
if( xStringResourceResolver.is() )
{
TypeClass eType = aPropertyValue.getValueType().getTypeClass();
if( eType == TypeClass_STRING )
{
OUString aPropStr;
aPropertyValue >>= aPropStr;
if( aPropStr.getLength() > 1 )
{
OUString aPureIdStr = aPropStr.copy( 1 );
if( xStringResourceResolver->hasEntryForId( aPureIdStr ) )
{
OUString aResourceStr = xStringResourceResolver->resolveString( aPureIdStr );
aPropertyValue <<= aResourceStr;
}
}
}
// StringItemList?
else if( eType == TypeClass_SEQUENCE )
{
Sequence< OUString > aStrings;
aPropertyValue >>= aStrings;
const OUString* pStrings = aStrings.getConstArray();
sal_Int32 nCount = aStrings.getLength();
std::vector< OUString > aResolvedStrings;
aResolvedStrings.resize( nCount );
try
{
for ( sal_Int32 i = 0; i < nCount; ++i )
{
OUString aIdStr = pStrings[i];
OUString aPureIdStr = aIdStr.copy( 1 );
if( xStringResourceResolver->hasEntryForId( aPureIdStr ) )
aResolvedStrings[i] = xStringResourceResolver->resolveString( aPureIdStr );
else
aResolvedStrings[i] = aIdStr;
}
}
2011-12-10 22:14:57 +09:00
catch( const resource::MissingResourceException & )
{}
aPropertyValue <<= comphelper::containerToSequence(aResolvedStrings);
}
}
else
impl_normalizePropertyValue_nothrow( aPropertyValue, nPropId );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
return aPropertyValue;
}
Any SAL_CALL FormComponentPropertyHandler::getPropertyValue( const OUString& _rPropertyName ) throw (UnknownPropertyException, RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
if( _rPropertyName == PROPERTY_ROWSET )
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
return ::comphelper::OPropertyContainer::getPropertyValue( _rPropertyName );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
::osl::MutexGuard aGuard( m_aMutex );
return impl_getPropertyValue_throw( _rPropertyName );
}
void SAL_CALL FormComponentPropertyHandler::setPropertyValue( const OUString& _rPropertyName, const Any& _rValue ) throw (UnknownPropertyException, RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
if( _rPropertyName == PROPERTY_ROWSET )
{
::comphelper::OPropertyContainer::setPropertyValue( _rPropertyName, _rValue );
return;
}
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
::osl::MutexGuard aGuard( m_aMutex );
PropertyId nPropId( impl_getPropertyId_throwUnknownProperty( _rPropertyName ) ); // check if property is known by the handler
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
Reference< graphic::XGraphicObject > xGrfObj;
if ( PROPERTY_ID_IMAGE_URL == nPropId && ( _rValue >>= xGrfObj ) )
{
DBG_ASSERT( xGrfObj.is(), "FormComponentPropertyHandler::setPropertyValue() xGrfObj is invalid");
OUString sObjectID( GRAPHOBJ_URLPREFIX );
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
sObjectID = sObjectID + xGrfObj->getUniqueID();
m_xComponent->setPropertyValue( _rPropertyName, uno::makeAny( sObjectID ) );
}
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
else if ( PROPERTY_ID_FONT == nPropId )
{
// special handling, the value is a faked value we generated ourself in impl_executeFontDialog_nothrow
Sequence< NamedValue > aFontPropertyValues;
OSL_VERIFY( _rValue >>= aFontPropertyValues );
const NamedValue* fontPropertyValue = aFontPropertyValues.getConstArray();
const NamedValue* fontPropertyValueEnd = fontPropertyValue + aFontPropertyValues.getLength();
for ( ; fontPropertyValue != fontPropertyValueEnd; ++fontPropertyValue )
m_xComponent->setPropertyValue( fontPropertyValue->Name, fontPropertyValue->Value );
}
else
{
Any aValue = _rValue;
Reference< resource::XStringResourceResolver > xStringResourceResolver
= lcl_getStringResourceResolverForProperty( m_xComponent, _rPropertyName, _rValue );
if( xStringResourceResolver.is() )
{
Reference< resource::XStringResourceManager >
xStringResourceManager( xStringResourceResolver, UNO_QUERY );
if( xStringResourceManager.is() )
{
Any aPropertyValue( m_xComponent->getPropertyValue( _rPropertyName ) );
TypeClass eType = aPropertyValue.getValueType().getTypeClass();
if( eType == TypeClass_STRING )
{
OUString aPropStr;
aPropertyValue >>= aPropStr;
if( aPropStr.getLength() > 1 )
{
OUString aPureIdStr = aPropStr.copy( 1 );
OUString aValueStr;
_rValue >>= aValueStr;
xStringResourceManager->setString( aPureIdStr, aValueStr );
aValue = aPropertyValue; // set value to force modified
}
}
// StringItemList?
else if( eType == TypeClass_SEQUENCE )
{
static const char aDot[] = ".";
static const char aEsc[] = "&";
// Put strings into resource using new ids
Sequence< OUString > aNewStrings;
_rValue >>= aNewStrings;
const OUString* pNewStrings = aNewStrings.getConstArray();
sal_Int32 nNewCount = aNewStrings.getLength();
// Create new Ids
std::unique_ptr<OUString[]> pNewPureIds(new OUString[nNewCount]);
OUString aIdStrBase = aDot;
Any aNameAny = m_xComponent->getPropertyValue(PROPERTY_NAME);
OUString sControlName;
aNameAny >>= sControlName;
aIdStrBase += sControlName;
aIdStrBase += aDot;
aIdStrBase += _rPropertyName;
sal_Int32 i;
OUString aDummyStr;
for ( i = 0; i < nNewCount; ++i )
{
sal_Int32 nUniqueId = xStringResourceManager->getUniqueNumericId();
OUString aPureIdStr = OUString::number( nUniqueId );
aPureIdStr += aIdStrBase;
pNewPureIds[i] = aPureIdStr;
// Force usage of next Unique Id
xStringResourceManager->setString( aPureIdStr, aDummyStr );
}
// Move strings to new Ids for all locales
Sequence< Locale > aLocaleSeq = xStringResourceManager->getLocales();
const Locale* pLocale = aLocaleSeq.getConstArray();
sal_Int32 nLocaleCount = aLocaleSeq.getLength();
Sequence< OUString > aOldIdStrings;
aPropertyValue >>= aOldIdStrings;
try
{
const OUString* pOldIdStrings = aOldIdStrings.getConstArray();
sal_Int32 nOldIdCount = aOldIdStrings.getLength();
for ( i = 0; i < nNewCount; ++i )
{
OUString aOldIdStr;
OUString aOldPureIdStr;
if( i < nOldIdCount )
{
aOldIdStr = pOldIdStrings[i];
aOldPureIdStr = aOldIdStr.copy( 1 );
}
OUString aNewPureIdStr = pNewPureIds[i];
for ( sal_Int32 iLocale = 0; iLocale < nLocaleCount; ++iLocale )
{
Locale aLocale = pLocale[iLocale];
OUString aResourceStr;
if( !aOldPureIdStr.isEmpty() )
{
if( xStringResourceManager->hasEntryForIdAndLocale( aOldPureIdStr, aLocale ) )
{
aResourceStr = xStringResourceManager->
resolveStringForLocale( aOldPureIdStr, aLocale );
}
}
xStringResourceManager->setStringForLocale( aNewPureIdStr, aResourceStr, aLocale );
}
}
}
2011-12-10 22:14:57 +09:00
catch( const resource::MissingResourceException & )
{}
// Set new strings for current locale and create
// new Id sequence as new property value
Sequence< OUString > aNewIdStrings;
aNewIdStrings.realloc( nNewCount );
OUString* pNewIdStrings = aNewIdStrings.getArray();
for ( i = 0; i < nNewCount; ++i )
{
OUString aPureIdStr = pNewPureIds[i];
OUString aStr = pNewStrings[i];
xStringResourceManager->setString( aPureIdStr, aStr );
OUString aIdStr = aEsc;
aIdStr += aPureIdStr;
pNewIdStrings[i] = aIdStr;
}
aValue <<= aNewIdStrings;
// Remove old ids from resource for all locales
const OUString* pOldIdStrings = aOldIdStrings.getConstArray();
sal_Int32 nOldIdCount = aOldIdStrings.getLength();
for( i = 0 ; i < nOldIdCount ; ++i )
{
OUString aIdStr = pOldIdStrings[i];
OUString aPureIdStr = aIdStr.copy( 1 );
for ( sal_Int32 iLocale = 0; iLocale < nLocaleCount; ++iLocale )
{
Locale aLocale = pLocale[iLocale];
try
{
xStringResourceManager->removeIdForLocale( aPureIdStr, aLocale );
}
2011-12-10 22:14:57 +09:00
catch( const resource::MissingResourceException & )
{}
}
}
}
}
}
m_xComponent->setPropertyValue( _rPropertyName, aValue );
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
Any SAL_CALL FormComponentPropertyHandler::convertToPropertyValue( const OUString& _rPropertyName, const Any& _rControlValue ) throw (UnknownPropertyException, RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
::osl::MutexGuard aGuard( m_aMutex );
PropertyId nPropId( impl_getPropertyId_throwUnknownProperty( _rPropertyName ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Property aProperty( impl_getPropertyFromId_throw( nPropId ) );
Any aPropertyValue( _rControlValue );
if ( !aPropertyValue.hasValue() )
{
if ( ( aProperty.Attributes & PropertyAttribute::MAYBEVOID ) == 0 )
// default construct an instance of the proper type
aPropertyValue = Any( nullptr, aProperty.Type );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// nothing to do
return aPropertyValue;
}
/// care for the special "default" string, translate it to VOID
if ( m_aPropertiesWithDefListEntry.find( _rPropertyName ) != m_aPropertiesWithDefListEntry.end() )
{
// it's a control with a string list
OUString sStringValue;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( _rControlValue >>= sStringValue )
{ // note that ColorListBoxes might transfer values either as string or as css.util.Color,
// so this check here is important
if ( sStringValue == m_sDefaultValueString )
return Any();
}
}
switch ( nPropId )
{
case PROPERTY_ID_DATASOURCE:
{
OUString sControlValue;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( _rControlValue >>= sControlValue );
if ( !sControlValue.isEmpty() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
Reference< XDatabaseContext > xDatabaseContext = sdb::DatabaseContext::create( m_xContext );
if ( !xDatabaseContext->hasByName( sControlValue ) )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
::svt::OFileNotation aTransformer(sControlValue);
aPropertyValue <<= OUString( aTransformer.get( ::svt::OFileNotation::N_URL ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
}
break; // case PROPERTY_ID_DATASOURCE
case PROPERTY_ID_SHOW_POSITION:
case PROPERTY_ID_SHOW_NAVIGATION:
case PROPERTY_ID_SHOW_RECORDACTIONS:
case PROPERTY_ID_SHOW_FILTERSORT:
{
OUString sControlValue;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( _rControlValue >>= sControlValue );
::std::vector< OUString > aListEntries;
tools::StringListResource aRes( PcrRes( RID_RSC_ENUM_SHOWHIDE ), aListEntries );
OSL_ENSURE( aListEntries.size() == 2, "FormComponentPropertyHandler::convertToPropertyValue: broken resource for Show/Hide!" );
bool bShow = ( aListEntries.size() < 2 ) || ( sControlValue == aListEntries[1] );
aPropertyValue <<= bShow;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
case PROPERTY_ID_TARGET_URL:
case PROPERTY_ID_IMAGE_URL:
{
OUString sControlValue;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( _rControlValue >>= sControlValue );
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
// Don't convert a placeholder
if ( nPropId == PROPERTY_ID_IMAGE_URL && sControlValue.equals( PcrRes(RID_EMBED_IMAGE_PLACEHOLDER).toString() ) )
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
aPropertyValue <<= sControlValue;
else
{
INetURLObject aDocURL( impl_getDocumentURL_nothrow() );
aPropertyValue <<= URIHelper::SmartRel2Abs( aDocURL, sControlValue, Link<OUString *, bool>(), false, true );
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
case PROPERTY_ID_DATEMIN:
case PROPERTY_ID_DATEMAX:
case PROPERTY_ID_DEFAULT_DATE:
case PROPERTY_ID_DATE:
{
util::Date aDate;
OSL_VERIFY( _rControlValue >>= aDate );
aPropertyValue <<= aDate;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
case PROPERTY_ID_TIMEMIN:
case PROPERTY_ID_TIMEMAX:
case PROPERTY_ID_DEFAULT_TIME:
case PROPERTY_ID_TIME:
{
util::Time aTime;
OSL_VERIFY( _rControlValue >>= aTime );
aPropertyValue <<= aTime;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
case PROPERTY_ID_WRITING_MODE:
{
aPropertyValue = FormComponentPropertyHandler_Base::convertToPropertyValue( _rPropertyName, _rControlValue );
sal_Int16 nNormalizedValue( 2 );
OSL_VERIFY( aPropertyValue >>= nNormalizedValue );
sal_Int16 nWritingMode = WritingMode2::CONTEXT;
switch ( nNormalizedValue )
{
case 0: nWritingMode = WritingMode2::LR_TB; break;
case 1: nWritingMode = WritingMode2::RL_TB; break;
case 2: nWritingMode = WritingMode2::CONTEXT; break;
default:
OSL_FAIL( "FormComponentPropertyHandler::convertToPropertyValue: unexpected 'normalized value' for WritingMode!" );
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
nWritingMode = WritingMode2::CONTEXT;
break;
}
aPropertyValue <<= nWritingMode;
}
break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
default:
aPropertyValue = FormComponentPropertyHandler_Base::convertToPropertyValue( _rPropertyName, _rControlValue );
break; // default
} // switch ( nPropId )
return aPropertyValue;
}
Any SAL_CALL FormComponentPropertyHandler::convertToControlValue( const OUString& _rPropertyName, const Any& _rPropertyValue, const Type& _rControlValueType ) throw (UnknownPropertyException, RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
::osl::MutexGuard aGuard( m_aMutex );
sal_Int32 nPropId = m_pInfoService->getPropertyId( _rPropertyName );
DBG_ASSERT( nPropId != -1, "FormComponentPropertyHandler::convertToPropertyValue: not one of my properties!!" );
impl_getPropertyFromId_throw( nPropId );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Any aControlValue( _rPropertyValue );
if ( !aControlValue.hasValue() )
{
// if the property is represented with a list box or color list box, we need to
// translate this into the string "Default"
if ( m_aPropertiesWithDefListEntry.find( _rPropertyName ) != m_aPropertiesWithDefListEntry.end() )
aControlValue <<= m_sDefaultValueString;
return aControlValue;
}
switch ( nPropId )
{
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_SHOW_POSITION:
case PROPERTY_ID_SHOW_NAVIGATION:
case PROPERTY_ID_SHOW_RECORDACTIONS:
case PROPERTY_ID_SHOW_FILTERSORT:
{
::std::vector< OUString > aListEntries;
tools::StringListResource aRes( PcrRes( RID_RSC_ENUM_SHOWHIDE ), aListEntries );
OSL_ENSURE( aListEntries.size() == 2, "FormComponentPropertyHandler::convertToControlValue: broken resource for Show/Hide!" );
if ( aListEntries.size() == 2 )
{
OUString sControlValue = ::comphelper::getBOOL( _rPropertyValue )
? aListEntries[1]
: aListEntries[0];
aControlValue <<= sControlValue;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_DATASOURCE:
{
OSL_ENSURE( _rControlValueType.getTypeClass() == TypeClass_STRING,
"FormComponentPropertyHandler::convertToControlValue: wrong ControlValueType!" );
OUString sDataSource;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
_rPropertyValue >>= sDataSource;
if ( !sDataSource.isEmpty() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
::svt::OFileNotation aTransformer( sDataSource );
sDataSource = aTransformer.get( ::svt::OFileNotation::N_SYSTEM );
}
aControlValue <<= sDataSource;
}
break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_CONTROLLABEL:
{
OUString sControlValue;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Reference< XPropertySet > xSet;
_rPropertyValue >>= xSet;
Reference< XPropertySetInfo > xPSI;
if ( xSet.is() )
xPSI = xSet->getPropertySetInfo();
if ( xPSI.is() && xPSI->hasPropertyByName( PROPERTY_LABEL ) )
{
OUStringBuffer aValue;
aValue.append( '<' );
OUString sLabel;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( xSet->getPropertyValue( PROPERTY_LABEL ) >>= sLabel );
aValue.append( sLabel );
aValue.append( '>' );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
sControlValue = aValue.makeStringAndClear();
}
aControlValue <<= sControlValue;
}
break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_DATEMIN:
case PROPERTY_ID_DATEMAX:
case PROPERTY_ID_DEFAULT_DATE:
case PROPERTY_ID_DATE:
{
sal_Int32 nDate = 0;
OSL_VERIFY( _rPropertyValue >>= nDate );
aControlValue <<= DBTypeConversion::toDate( nDate );
}
break;
case PROPERTY_ID_TIMEMIN:
case PROPERTY_ID_TIMEMAX:
case PROPERTY_ID_DEFAULT_TIME:
case PROPERTY_ID_TIME:
{
sal_Int64 nTime = 0;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( _rPropertyValue >>= nTime );
aControlValue <<= DBTypeConversion::toTime( nTime );
}
break;
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
case PROPERTY_ID_WRITING_MODE:
{
sal_Int16 nWritingMode( WritingMode2::CONTEXT );
OSL_VERIFY( _rPropertyValue >>= nWritingMode );
sal_Int16 nNormalized = 2;
switch ( nWritingMode )
{
case WritingMode2::LR_TB: nNormalized = 0; break;
case WritingMode2::RL_TB: nNormalized = 1; break;
case WritingMode2::CONTEXT: nNormalized = 2; break;
default:
OSL_FAIL( "FormComponentPropertyHandler::convertToControlValue: unsupported API value for WritingMode!" );
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
nNormalized = 2;
break;
}
aControlValue = FormComponentPropertyHandler_Base::convertToControlValue( _rPropertyName, makeAny( nNormalized ), _rControlValueType );
}
break;
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
case PROPERTY_ID_FONT:
{
FontDescriptor aFont;
OSL_VERIFY( _rPropertyValue >>= aFont );
OUStringBuffer displayName;
if ( aFont.Name.isEmpty() )
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
{
displayName.append( PcrRes(RID_STR_FONT_DEFAULT).toString() );
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
}
else
{
// font name
displayName.append( aFont.Name );
displayName.append( ", " );
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
// font style
::FontWeight eWeight = VCLUnoHelper::ConvertFontWeight( aFont.Weight );
sal_uInt16 nStyleResID = RID_STR_FONTSTYLE_REGULAR;
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
if ( aFont.Slant == FontSlant_ITALIC )
{
if ( eWeight > WEIGHT_NORMAL )
nStyleResID = RID_STR_FONTSTYLE_BOLD_ITALIC;
else
nStyleResID = RID_STR_FONTSTYLE_ITALIC;
}
else
{
if ( eWeight > WEIGHT_NORMAL )
nStyleResID = RID_STR_FONTSTYLE_BOLD;
}
displayName.append(PcrRes(nStyleResID).toString());
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
// font size
if ( aFont.Height )
{
displayName.append( ", " );
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
displayName.append( sal_Int32( aFont.Height ) );
}
}
aControlValue <<= displayName.makeStringAndClear();
}
break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
default:
aControlValue = FormComponentPropertyHandler_Base::convertToControlValue( _rPropertyName, _rPropertyValue, _rControlValueType );
break;
} // switch ( nPropId )
return aControlValue;
}
PropertyState SAL_CALL FormComponentPropertyHandler::getPropertyState( const OUString& _rPropertyName ) throw (UnknownPropertyException, RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
::osl::MutexGuard aGuard( m_aMutex );
if ( m_xPropertyState.is() )
return m_xPropertyState->getPropertyState( _rPropertyName );
return PropertyState_DIRECT_VALUE;
}
void SAL_CALL FormComponentPropertyHandler::addPropertyChangeListener( const Reference< XPropertyChangeListener >& _rxListener ) throw (NullPointerException, RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
::osl::MutexGuard aGuard( m_aMutex );
FormComponentPropertyHandler_Base::addPropertyChangeListener( _rxListener );
if ( m_xComponent.is() )
m_xComponent->addPropertyChangeListener( OUString(), _rxListener );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
void SAL_CALL FormComponentPropertyHandler::removePropertyChangeListener( const Reference< XPropertyChangeListener >& _rxListener ) throw (RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
::osl::MutexGuard aGuard( m_aMutex );
if ( m_xComponent.is() )
m_xComponent->removePropertyChangeListener( OUString(), _rxListener );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
FormComponentPropertyHandler_Base::removePropertyChangeListener( _rxListener );
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
void FormComponentPropertyHandler::onNewComponent()
{
FormComponentPropertyHandler_Base::onNewComponent();
if ( !m_xComponentPropertyInfo.is() && m_xComponent.is() )
throw NullPointerException();
m_xPropertyState.set( m_xComponent, UNO_QUERY );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
m_eComponentClass = eUnknown;
m_bComponentIsSubForm = m_bHaveListSource = m_bHaveCommand = false;
m_nClassId = 0;
impl_initComponentMetaData_throw();
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Sequence< Property > SAL_CALL FormComponentPropertyHandler::doDescribeSupportedProperties() const
{
if ( !m_xComponentPropertyInfo.is() )
return Sequence< Property >();
::std::vector< Property > aProperties;
Sequence< Property > aAllProperties( m_xComponentPropertyInfo->getProperties() );
aProperties.reserve( aAllProperties.getLength() );
// filter the properties
PropertyId nPropId( 0 );
OUString sDisplayName;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Property* pProperty = aAllProperties.getArray();
Property* pPropertiesEnd = pProperty + aAllProperties.getLength();
for ( ; pProperty != pPropertiesEnd; ++pProperty )
{
nPropId = m_pInfoService->getPropertyId( pProperty->Name );
if ( nPropId == -1 )
continue;
pProperty->Handle = nPropId;
sDisplayName = m_pInfoService->getPropertyTranslation( nPropId );
if ( sDisplayName.isEmpty() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
continue;
sal_uInt32 nPropertyUIFlags = m_pInfoService->getPropertyUIFlags( nPropId );
bool bIsVisibleForForms = ( nPropertyUIFlags & PROP_FLAG_FORM_VISIBLE ) != 0;
bool bIsVisibleForDialogs = ( nPropertyUIFlags & PROP_FLAG_DIALOG_VISIBLE ) != 0;
// depending on whether we're working for a form or a UNO dialog, some
// properties are not displayed
if ( ( m_eComponentClass == eFormControl && !bIsVisibleForForms )
|| ( m_eComponentClass == eDialogControl && !bIsVisibleForDialogs )
)
continue;
// some generic sanity checks
if ( impl_shouldExcludeProperty_nothrow( *pProperty ) )
continue;
switch ( nPropId )
{
case PROPERTY_ID_BORDER:
case PROPERTY_ID_TABSTOP:
// BORDER and TABSTOP are normalized (see impl_normalizePropertyValue_nothrow)
// to not allow VOID values
pProperty->Attributes &= ~( PropertyAttribute::MAYBEVOID );
break;
case PROPERTY_ID_LISTSOURCE:
// no cursor source if no Base is installed. #124939#
// This fix is not intendend to appear on the main trunk. If you find it there,
// please tell me! frank.schoenheit@sun.com
if ( SvtModuleOptions().IsModuleInstalled( SvtModuleOptions::EModule::DATABASE ) )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
const_cast< FormComponentPropertyHandler* >( this )->m_bHaveListSource = true;
break;
case PROPERTY_ID_COMMAND:
// no cursor source if no Base is installed. #124939#
// This fix is not intendend to appear on the main trunk. If you find it there,
// please tell me! frank.schoenheit@sun.com
if ( SvtModuleOptions().IsModuleInstalled( SvtModuleOptions::EModule::DATABASE ) )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
const_cast< FormComponentPropertyHandler* >( this )->m_bHaveCommand = true;
break;
} // switch ( nPropId )
aProperties.push_back( *pProperty );
}
if ( aProperties.empty() )
return Sequence< Property >();
return Sequence< Property >( &(*aProperties.begin()), aProperties.size() );
}
Sequence< OUString > SAL_CALL FormComponentPropertyHandler::getSupersededProperties( ) throw (RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
return Sequence< OUString >( );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
Sequence< OUString > SAL_CALL FormComponentPropertyHandler::getActuatingProperties( ) throw (RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
::osl::MutexGuard aGuard( m_aMutex );
::std::vector< OUString > aInterestingProperties;
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_DATASOURCE) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_COMMAND) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_COMMANDTYPE) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_LISTSOURCE) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_LISTSOURCETYPE) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_SUBMIT_ENCODING) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_REPEAT) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_TABSTOP) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_BORDER) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_CONTROLSOURCE) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_DROPDOWN) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_IMAGE_URL) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_TARGET_URL) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_STRINGITEMLIST) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_BUTTONTYPE) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_ESCAPE_PROCESSING) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_TRISTATE) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_DECIMAL_ACCURACY) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_SHOWTHOUSANDSEP) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_FORMATKEY) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_EMPTY_IS_NULL) );
aInterestingProperties.push_back( static_cast<const OUString&>(PROPERTY_TOGGLE) );
return Sequence< OUString >( &(*aInterestingProperties.begin()), aInterestingProperties.size() );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
LineDescriptor SAL_CALL FormComponentPropertyHandler::describePropertyLine( const OUString& _rPropertyName,
const Reference< XPropertyControlFactory >& _rxControlFactory )
throw (UnknownPropertyException, NullPointerException, RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
if ( !_rxControlFactory.is() )
throw NullPointerException();
::osl::MutexGuard aGuard( m_aMutex );
PropertyId nPropId( impl_getPropertyId_throwUnknownProperty( _rPropertyName ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Property aProperty( impl_getPropertyFromId_throw( nPropId ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// for the MultiLine property, we have different UI translations depending on the control
// type
if ( nPropId == PROPERTY_ID_MULTILINE )
{
if ( ( m_nClassId == FormComponentType::FIXEDTEXT )
|| ( m_nClassId == FormComponentType::COMMANDBUTTON )
|| ( m_nClassId == FormComponentType::RADIOBUTTON )
|| ( m_nClassId == FormComponentType::CHECKBOX )
)
nPropId = PROPERTY_ID_WORDBREAK;
}
OUString sDisplayName = m_pInfoService->getPropertyTranslation( nPropId );
if ( sDisplayName.isEmpty() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
2011-03-01 17:55:09 +01:00
OSL_FAIL( "FormComponentPropertyHandler::describePropertyLine: did getSupportedProperties not work properly?" );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
throw UnknownPropertyException();
}
LineDescriptor aDescriptor;
aDescriptor.HelpURL = HelpIdUrl::getHelpURL( m_pInfoService->getPropertyHelpId( nPropId ) );
aDescriptor.DisplayName = sDisplayName;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// for the moment, assume a text field
sal_Int16 nControlType = PropertyControlType::TextField;
bool bReadOnly = false;
aDescriptor.Control.clear();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool bNeedDefaultStringIfVoidAllowed = false;
TypeClass eType = aProperty.Type.getTypeClass();
switch ( nPropId )
{
case PROPERTY_ID_DEFAULT_SELECT_SEQ:
case PROPERTY_ID_SELECTEDITEMS:
aDescriptor.PrimaryButtonId = UID_PROP_DLG_SELECTION;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
case PROPERTY_ID_FILTER:
aDescriptor.PrimaryButtonId = UID_PROP_DLG_FILTER;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
case PROPERTY_ID_SORT:
aDescriptor.PrimaryButtonId = UID_PROP_DLG_ORDER;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
case PROPERTY_ID_MASTERFIELDS:
case PROPERTY_ID_DETAILFIELDS:
nControlType = PropertyControlType::StringListField;
aDescriptor.PrimaryButtonId = UID_PROP_DLG_FORMLINKFIELDS;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
case PROPERTY_ID_COMMAND:
aDescriptor.PrimaryButtonId = UID_PROP_DLG_SQLCOMMAND;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
case PROPERTY_ID_TABINDEX:
{
Reference< XControlContainer > xControlContext( impl_getContextControlContainer_nothrow() );
if ( xControlContext.is() )
aDescriptor.PrimaryButtonId = UID_PROP_DLG_TABINDEX;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
nControlType = PropertyControlType::NumericField;
};
break;
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
case PROPERTY_ID_FONT:
bReadOnly = true;
aDescriptor.PrimaryButtonId = UID_PROP_DLG_FONT_TYPE;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
case PROPERTY_ID_TARGET_URL:
case PROPERTY_ID_IMAGE_URL:
{
aDescriptor.Control = new OFileUrlControl( impl_getDefaultDialogParent_nothrow(), WB_TABSTOP | WB_BORDER );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
aDescriptor.PrimaryButtonId = PROPERTY_ID_TARGET_URL == nPropId
? OUString(UID_PROP_DLG_ATTR_TARGET_URL)
: OUString(UID_PROP_DLG_IMAGE_URL);
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
case PROPERTY_ID_ECHO_CHAR:
nControlType = PropertyControlType::CharacterField;
break;
case PROPERTY_ID_BACKGROUNDCOLOR:
case PROPERTY_ID_FILLCOLOR:
case PROPERTY_ID_SYMBOLCOLOR:
case PROPERTY_ID_BORDERCOLOR:
nControlType = PropertyControlType::ColorListBox;
switch( nPropId )
{
case PROPERTY_ID_BACKGROUNDCOLOR:
aDescriptor.PrimaryButtonId = UID_PROP_DLG_BACKGROUNDCOLOR; break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_FILLCOLOR:
aDescriptor.PrimaryButtonId = UID_PROP_DLG_FILLCOLOR; break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_SYMBOLCOLOR:
aDescriptor.PrimaryButtonId = UID_PROP_DLG_SYMBOLCOLOR; break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_BORDERCOLOR:
aDescriptor.PrimaryButtonId = UID_PROP_DLG_BORDERCOLOR; break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
case PROPERTY_ID_LABEL:
nControlType = PropertyControlType::MultiLineTextField;
break;
case PROPERTY_ID_DEFAULT_TEXT:
{
if (FormComponentType::FILECONTROL == m_nClassId)
nControlType = PropertyControlType::TextField;
else
nControlType = PropertyControlType::MultiLineTextField;
}
break;
case PROPERTY_ID_TEXT:
if ( impl_componentHasProperty_throw( PROPERTY_MULTILINE ) )
nControlType = PropertyControlType::MultiLineTextField;
break;
case PROPERTY_ID_CONTROLLABEL:
bReadOnly = true;
aDescriptor.PrimaryButtonId = UID_PROP_DLG_CONTROLLABEL;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
case PROPERTY_ID_FORMATKEY:
case PROPERTY_ID_EFFECTIVE_MIN:
case PROPERTY_ID_EFFECTIVE_MAX:
case PROPERTY_ID_EFFECTIVE_DEFAULT:
case PROPERTY_ID_EFFECTIVE_VALUE:
{
// and the supplier is really available
Reference< XNumberFormatsSupplier > xSupplier;
m_xComponent->getPropertyValue( PROPERTY_FORMATSSUPPLIER ) >>= xSupplier;
if (xSupplier.is())
{
Reference< XUnoTunnel > xTunnel(xSupplier,UNO_QUERY);
DBG_ASSERT(xTunnel.is(), "FormComponentPropertyHandler::describePropertyLine : xTunnel is invalid!");
SvNumberFormatsSupplierObj* pSupplier = reinterpret_cast<SvNumberFormatsSupplierObj*>(xTunnel->getSomething(SvNumberFormatsSupplierObj::getUnoTunnelId()));
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if (pSupplier != nullptr)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
bool bIsFormatKey = (PROPERTY_ID_FORMATKEY == nPropId);
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bReadOnly = bIsFormatKey;
if ( bIsFormatKey )
{
OFormatSampleControl* pControl = new OFormatSampleControl( impl_getDefaultDialogParent_nothrow(), WB_READONLY | WB_TABSTOP | WB_BORDER );
aDescriptor.Control = pControl;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
pControl->SetFormatSupplier( pSupplier );
aDescriptor.PrimaryButtonId = UID_PROP_DLG_NUMBER_FORMAT;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
else
{
OFormattedNumericControl* pControl = new OFormattedNumericControl( impl_getDefaultDialogParent_nothrow(), WB_TABSTOP | WB_BORDER );
aDescriptor.Control = pControl;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
FormatDescription aDesc;
aDesc.pSupplier = pSupplier;
Any aFormatKeyValue = m_xComponent->getPropertyValue(PROPERTY_FORMATKEY);
if ( !( aFormatKeyValue >>= aDesc.nKey ) )
aDesc.nKey = 0;
pControl->SetFormatDescription( aDesc );
}
}
}
}
break;
case PROPERTY_ID_DATEMIN:
case PROPERTY_ID_DATEMAX:
case PROPERTY_ID_DEFAULT_DATE:
case PROPERTY_ID_DATE:
nControlType = PropertyControlType::DateField;
break;
case PROPERTY_ID_TIMEMIN:
case PROPERTY_ID_TIMEMAX:
case PROPERTY_ID_DEFAULT_TIME:
case PROPERTY_ID_TIME:
nControlType = PropertyControlType::TimeField;
break;
case PROPERTY_ID_VALUEMIN:
case PROPERTY_ID_VALUEMAX:
case PROPERTY_ID_DEFAULT_VALUE:
case PROPERTY_ID_VALUE:
{
OFormattedNumericControl* pControl = new OFormattedNumericControl( impl_getDefaultDialogParent_nothrow(), WB_TABSTOP | WB_BORDER | WB_SPIN | WB_REPEAT );
aDescriptor.Control = pControl;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// we don't set a formatter so the control uses a default (which uses the application
// language and a default numeric format)
// but we set the decimal digits
pControl->SetDecimalDigits(
::comphelper::getINT16( m_xComponent->getPropertyValue( PROPERTY_DECIMAL_ACCURACY ) )
);
// and the thousands separator
pControl->SetThousandsSep(
::comphelper::getBOOL( m_xComponent->getPropertyValue(PROPERTY_SHOWTHOUSANDSEP) )
);
// and the default value for the property
try
{
if (m_xPropertyState.is() && ((PROPERTY_ID_VALUEMIN == nPropId) || (PROPERTY_ID_VALUEMAX == nPropId)))
{
double nDefault = 0;
if ( m_xPropertyState->getPropertyDefault( aProperty.Name ) >>= nDefault )
pControl->SetDefaultValue( nDefault );
}
}
2011-12-10 22:14:57 +09:00
catch (const Exception&)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
// just ignore it
}
// and allow empty values only for the default value and the value
pControl->EnableEmptyField( ( PROPERTY_ID_DEFAULT_VALUE == nPropId )
|| ( PROPERTY_ID_VALUE == nPropId ) );
}
break;
default:
if ( TypeClass_BYTE <= eType && eType <= TypeClass_DOUBLE )
{
sal_Int16 nDigits = 0;
sal_Int16 nValueUnit = -1;
sal_Int16 nDisplayUnit = -1;
if ( m_eComponentClass == eFormControl )
{
if ( ( nPropId == PROPERTY_ID_WIDTH )
|| ( nPropId == PROPERTY_ID_ROWHEIGHT )
|| ( nPropId == PROPERTY_ID_HEIGHT )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
)
{
nValueUnit = MeasureUnit::MM_10TH;
nDisplayUnit = impl_getDocumentMeasurementUnit_throw();
nDigits = 2;
}
}
Optional< double > aValueNotPresent( sal_False, 0 );
aDescriptor.Control = PropertyHandlerHelper::createNumericControl(
_rxControlFactory, nDigits, aValueNotPresent, aValueNotPresent, false );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Reference< XNumericControl > xNumericControl( aDescriptor.Control, UNO_QUERY_THROW );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( nValueUnit != -1 )
xNumericControl->setValueUnit( nValueUnit );
if ( nDisplayUnit != -1 )
xNumericControl->setDisplayUnit( nDisplayUnit );
}
break;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( eType == TypeClass_SEQUENCE )
nControlType = PropertyControlType::StringListField;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// boolean values
if ( eType == TypeClass_BOOLEAN )
{
sal_uInt16 nResId = RID_RSC_ENUM_YESNO;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( ( nPropId == PROPERTY_ID_SHOW_POSITION )
|| ( nPropId == PROPERTY_ID_SHOW_NAVIGATION )
|| ( nPropId == PROPERTY_ID_SHOW_RECORDACTIONS )
|| ( nPropId == PROPERTY_ID_SHOW_FILTERSORT )
)
CWS-TOOLING: integrate CWS dba31f 2008-12-10 14:16:09 +0100 oj r265185 : #i96658# remove is 2008-12-10 08:46:07 +0100 oj r265147 : remove duplicate ids 2008-12-10 08:35:02 +0100 oj r265146 : #i96658# remove is 2008-12-09 11:44:35 +0100 oj r265072 : use of tools::StringresourceList 2008-12-09 11:43:41 +0100 oj r265071 : new class to read string elements from a Resource 2008-12-09 11:41:56 +0100 oj r265070 : export StringListResource 2008-12-09 11:38:17 +0100 oj r265068 : change string ; to more string objects 2008-12-08 12:11:43 +0100 oj r264985 : change default-license-id to lic-en-US 2008-12-05 12:06:09 +0100 oj r264896 : disable check to uncheck 2008-12-04 08:58:50 +0100 oj r264814 : #i96517,i96520,i96522# d&d, background, state fixed 2008-12-04 08:53:29 +0100 oj r264813 : #i96434# use document ui name from filter 2008-12-04 08:41:06 +0100 oj r264812 : #i96434# use document ui name from filter 2008-12-02 13:48:49 +0100 lla r264697 : #i96526# extra string for default otr wasn't found 2008-11-28 11:46:31 +0100 oj r264536 : move toolbar and resize add field dlg 2008-11-28 08:38:22 +0100 oj r264526 : load string resources 2008-11-27 19:28:52 +0100 oj r264520 : unsigned 2008-11-27 19:10:19 +0100 oj r264517 : move class into unnamed namespace 2008-11-27 18:33:38 +0100 oj r264514 : wrong param 2008-11-27 16:52:39 +0100 oj r264510 : #i96622# wrong string replacement 2008-11-27 16:46:03 +0100 oj r264509 : remove unused var 2008-11-27 13:37:16 +0100 oj r264484 : #i96432# notify only when not in special mode of the page 2008-11-27 13:16:47 +0100 oj r264479 : #i95224# accept alias in group by 2008-11-27 12:35:19 +0100 oj r264477 : #i95416# always show localized strings in the start marker 2008-11-27 09:49:29 +0100 oj r264455 : #i93460# set split pos 2008-11-27 09:05:27 +0100 oj r264447 : #i96453# use extension from mimetype / mediatype 2008-11-26 16:24:43 +0100 oj r264416 : #i96520# #i96522# #i96519# some changes at the add field dialog 2008-11-26 16:20:27 +0100 oj r264414 : #i93420# prevent to register a none system file url 2008-11-26 16:19:02 +0100 oj r264413 : #i96522# new class to paste multiple objects 2008-11-26 10:06:12 +0100 oj r264349 : #i96191# introduce new error message and check if type was defined aand should not be changed 2008-11-26 10:06:12 +0100 oj r264348 : #i96191# throw error when decimal is to big 2008-11-25 12:08:59 +0100 oj r264281 : #i96431# correct state for align and move 2008-11-25 11:54:47 +0100 oj r264280 : #i96428# when new bind to first table 2008-11-25 11:49:55 +0100 oj r264279 : #i96434# add report output format to inspection 2008-11-25 11:49:05 +0100 oj r264278 : #i96434# add report output format to inspection 2008-11-24 10:46:23 +0100 oj r264215 : #i96458# size width for controls 2008-11-24 09:28:56 +0100 oj r264199 : #i96459# mark detail section when nothing is selected 2008-11-20 12:02:35 +0100 oj r264038 : #i96191# fix check for prec 2008-11-20 08:06:32 +0100 oj r264026 : #i90949# patch MID function 2008-11-11 13:14:58 +0100 oj r263555 : #i96086# apply patch 2008-11-11 11:34:46 +0100 oj r263549 : #i94128# correct height of section when controls moved outside 2008-11-11 07:52:08 +0100 oj r263544 : #i94729# fix string with ; as sep 2008-11-11 07:45:27 +0100 oj r263543 : #i95222# export chart title style 2008-11-11 07:43:37 +0100 oj r263542 : #i92541# fix line height
2008-12-10 13:41:25 +00:00
nResId = RID_RSC_ENUM_SHOWHIDE;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
::std::vector< OUString > aListEntries;
CWS-TOOLING: integrate CWS dba31f 2008-12-10 14:16:09 +0100 oj r265185 : #i96658# remove is 2008-12-10 08:46:07 +0100 oj r265147 : remove duplicate ids 2008-12-10 08:35:02 +0100 oj r265146 : #i96658# remove is 2008-12-09 11:44:35 +0100 oj r265072 : use of tools::StringresourceList 2008-12-09 11:43:41 +0100 oj r265071 : new class to read string elements from a Resource 2008-12-09 11:41:56 +0100 oj r265070 : export StringListResource 2008-12-09 11:38:17 +0100 oj r265068 : change string ; to more string objects 2008-12-08 12:11:43 +0100 oj r264985 : change default-license-id to lic-en-US 2008-12-05 12:06:09 +0100 oj r264896 : disable check to uncheck 2008-12-04 08:58:50 +0100 oj r264814 : #i96517,i96520,i96522# d&d, background, state fixed 2008-12-04 08:53:29 +0100 oj r264813 : #i96434# use document ui name from filter 2008-12-04 08:41:06 +0100 oj r264812 : #i96434# use document ui name from filter 2008-12-02 13:48:49 +0100 lla r264697 : #i96526# extra string for default otr wasn't found 2008-11-28 11:46:31 +0100 oj r264536 : move toolbar and resize add field dlg 2008-11-28 08:38:22 +0100 oj r264526 : load string resources 2008-11-27 19:28:52 +0100 oj r264520 : unsigned 2008-11-27 19:10:19 +0100 oj r264517 : move class into unnamed namespace 2008-11-27 18:33:38 +0100 oj r264514 : wrong param 2008-11-27 16:52:39 +0100 oj r264510 : #i96622# wrong string replacement 2008-11-27 16:46:03 +0100 oj r264509 : remove unused var 2008-11-27 13:37:16 +0100 oj r264484 : #i96432# notify only when not in special mode of the page 2008-11-27 13:16:47 +0100 oj r264479 : #i95224# accept alias in group by 2008-11-27 12:35:19 +0100 oj r264477 : #i95416# always show localized strings in the start marker 2008-11-27 09:49:29 +0100 oj r264455 : #i93460# set split pos 2008-11-27 09:05:27 +0100 oj r264447 : #i96453# use extension from mimetype / mediatype 2008-11-26 16:24:43 +0100 oj r264416 : #i96520# #i96522# #i96519# some changes at the add field dialog 2008-11-26 16:20:27 +0100 oj r264414 : #i93420# prevent to register a none system file url 2008-11-26 16:19:02 +0100 oj r264413 : #i96522# new class to paste multiple objects 2008-11-26 10:06:12 +0100 oj r264349 : #i96191# introduce new error message and check if type was defined aand should not be changed 2008-11-26 10:06:12 +0100 oj r264348 : #i96191# throw error when decimal is to big 2008-11-25 12:08:59 +0100 oj r264281 : #i96431# correct state for align and move 2008-11-25 11:54:47 +0100 oj r264280 : #i96428# when new bind to first table 2008-11-25 11:49:55 +0100 oj r264279 : #i96434# add report output format to inspection 2008-11-25 11:49:05 +0100 oj r264278 : #i96434# add report output format to inspection 2008-11-24 10:46:23 +0100 oj r264215 : #i96458# size width for controls 2008-11-24 09:28:56 +0100 oj r264199 : #i96459# mark detail section when nothing is selected 2008-11-20 12:02:35 +0100 oj r264038 : #i96191# fix check for prec 2008-11-20 08:06:32 +0100 oj r264026 : #i90949# patch MID function 2008-11-11 13:14:58 +0100 oj r263555 : #i96086# apply patch 2008-11-11 11:34:46 +0100 oj r263549 : #i94128# correct height of section when controls moved outside 2008-11-11 07:52:08 +0100 oj r263544 : #i94729# fix string with ; as sep 2008-11-11 07:45:27 +0100 oj r263543 : #i95222# export chart title style 2008-11-11 07:43:37 +0100 oj r263542 : #i92541# fix line height
2008-12-10 13:41:25 +00:00
tools::StringListResource aRes(PcrRes(nResId),aListEntries);
aDescriptor.Control = PropertyHandlerHelper::createListBoxControl( _rxControlFactory, aListEntries, false, false );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bNeedDefaultStringIfVoidAllowed = true;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// enum properties
sal_uInt32 nPropertyUIFlags = m_pInfoService->getPropertyUIFlags( nPropId );
bool bIsEnumProperty = ( nPropertyUIFlags & PROP_FLAG_ENUM ) != 0;
if ( bIsEnumProperty || ( PROPERTY_ID_TARGET_FRAME == nPropId ) )
{
::std::vector< OUString > aEnumValues = m_pInfoService->getPropertyEnumRepresentations( nPropId );
::std::vector< OUString >::const_iterator pStart = aEnumValues.begin();
::std::vector< OUString >::const_iterator pEnd = aEnumValues.end();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// for a checkbox: if "ambiguous" is not allowed, remove this from the sequence
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
if ( ( PROPERTY_ID_DEFAULT_STATE == nPropId )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
|| ( PROPERTY_ID_STATE == nPropId )
)
CWS-TOOLING: integrate CWS cmcfixes51 2008-12-08 10:12:55 +0100 cmc r264975 : #i96203# protect with ifdefs to avoid unused symbol on mac 2008-12-05 12:23:47 +0100 cmc r264898 : CWS-TOOLING: rebase CWS cmcfixes51 to trunk@264807 (milestone: DEV300:m37) 2008-12-01 14:45:17 +0100 cmc r264606 : #i76655# ehlos apparently required 2008-11-28 17:49:30 +0100 cmc r264567 : #i96655# remove newly unused method 2008-11-28 10:41:28 +0100 cmc r264531 : #i96647# better ppc-bridges flushCode impl 2008-11-27 12:58:40 +0100 cmc r264478 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 12:32:49 +0100 cmc r264476 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 12:26:02 +0100 cmc r264475 : #i96655# redundant old table export helpers 2008-11-27 11:49:06 +0100 cmc r264473 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:38:35 +0100 cmc r264471 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:14:21 +0100 cmc r264467 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:06:22 +0100 cmc r264464 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:58:18 +0100 cmc r264462 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:41:44 +0100 cmc r264461 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:19:24 +0100 cmc r264460 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:13:39 +0100 cmc r264459 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:06:14 +0100 cmc r264458 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:59:54 +0100 cmc r264457 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:52:51 +0100 cmc r264456 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:48:26 +0100 cmc r264454 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:40:20 +0100 cmc r264452 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:35:26 +0100 cmc r264451 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:31:00 +0100 cmc r264450 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:24:08 +0100 cmc r264449 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:26:15 +0100 cmc r264443 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:21:01 +0100 cmc r264442 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:09:40 +0100 cmc r264441 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 23:51:56 +0100 cmc r264440 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 23:49:09 +0100 cmc r264439 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 18:09:54 +0100 cmc r264432 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 18:07:40 +0100 cmc r264431 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:28:02 +0100 cmc r264429 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:27:39 +0100 cmc r264428 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:18:36 +0100 cmc r264426 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 16:22:16 +0100 cmc r264415 : #i96624# make implicit braces and brackets explicit to avoid warnings 2008-11-26 16:00:23 +0100 cmc r264409 : #i90426# remove warnings from svtools 2008-11-26 15:59:17 +0100 cmc r264408 : #i90426# remove warnings 2008-11-26 15:47:32 +0100 cmc r264404 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:46:57 +0100 cmc r264394 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:19:50 +0100 cmc r264387 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:15:26 +0100 cmc r264386 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:11:26 +0100 cmc r264384 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 13:44:23 +0100 cmc r264380 : #i96084# comfirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 13:12:24 +0100 cmc r264372 : #i96604# silence new warnings 2008-11-26 12:35:02 +0100 cmc r264369 : #i96203# make qstarter work in 3-layer land 2008-11-26 12:33:04 +0100 cmc r264368 : #i96170# ensure gtypes are up and running
2008-12-11 07:05:03 +00:00
{
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( impl_componentHasProperty_throw( PROPERTY_TRISTATE ) )
{
if ( !::comphelper::getBOOL( m_xComponent->getPropertyValue( PROPERTY_TRISTATE ) ) )
{ // remove the last sequence element
if ( pEnd > pStart )
--pEnd;
}
}
else
--pEnd;
CWS-TOOLING: integrate CWS cmcfixes51 2008-12-08 10:12:55 +0100 cmc r264975 : #i96203# protect with ifdefs to avoid unused symbol on mac 2008-12-05 12:23:47 +0100 cmc r264898 : CWS-TOOLING: rebase CWS cmcfixes51 to trunk@264807 (milestone: DEV300:m37) 2008-12-01 14:45:17 +0100 cmc r264606 : #i76655# ehlos apparently required 2008-11-28 17:49:30 +0100 cmc r264567 : #i96655# remove newly unused method 2008-11-28 10:41:28 +0100 cmc r264531 : #i96647# better ppc-bridges flushCode impl 2008-11-27 12:58:40 +0100 cmc r264478 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 12:32:49 +0100 cmc r264476 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 12:26:02 +0100 cmc r264475 : #i96655# redundant old table export helpers 2008-11-27 11:49:06 +0100 cmc r264473 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:38:35 +0100 cmc r264471 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:14:21 +0100 cmc r264467 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:06:22 +0100 cmc r264464 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:58:18 +0100 cmc r264462 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:41:44 +0100 cmc r264461 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:19:24 +0100 cmc r264460 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:13:39 +0100 cmc r264459 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:06:14 +0100 cmc r264458 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:59:54 +0100 cmc r264457 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:52:51 +0100 cmc r264456 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:48:26 +0100 cmc r264454 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:40:20 +0100 cmc r264452 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:35:26 +0100 cmc r264451 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:31:00 +0100 cmc r264450 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:24:08 +0100 cmc r264449 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:26:15 +0100 cmc r264443 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:21:01 +0100 cmc r264442 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:09:40 +0100 cmc r264441 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 23:51:56 +0100 cmc r264440 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 23:49:09 +0100 cmc r264439 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 18:09:54 +0100 cmc r264432 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 18:07:40 +0100 cmc r264431 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:28:02 +0100 cmc r264429 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:27:39 +0100 cmc r264428 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:18:36 +0100 cmc r264426 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 16:22:16 +0100 cmc r264415 : #i96624# make implicit braces and brackets explicit to avoid warnings 2008-11-26 16:00:23 +0100 cmc r264409 : #i90426# remove warnings from svtools 2008-11-26 15:59:17 +0100 cmc r264408 : #i90426# remove warnings 2008-11-26 15:47:32 +0100 cmc r264404 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:46:57 +0100 cmc r264394 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:19:50 +0100 cmc r264387 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:15:26 +0100 cmc r264386 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:11:26 +0100 cmc r264384 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 13:44:23 +0100 cmc r264380 : #i96084# comfirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 13:12:24 +0100 cmc r264372 : #i96604# silence new warnings 2008-11-26 12:35:02 +0100 cmc r264369 : #i96203# make qstarter work in 3-layer land 2008-11-26 12:33:04 +0100 cmc r264368 : #i96170# ensure gtypes are up and running
2008-12-11 07:05:03 +00:00
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( PROPERTY_ID_LISTSOURCETYPE == nPropId )
if ( FormComponentType::COMBOBOX == m_nClassId )
// remove the first sequence element -> value list not possible for combo boxes
++pStart;
// copy the sequence
::std::vector< OUString > aListEntries( pEnd - pStart );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
::std::copy( pStart, pEnd, aListEntries.begin() );
// create the control
if ( PROPERTY_ID_TARGET_FRAME == nPropId )
aDescriptor.Control = PropertyHandlerHelper::createComboBoxControl( _rxControlFactory, aListEntries, false, false );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
else
{
aDescriptor.Control = PropertyHandlerHelper::createListBoxControl( _rxControlFactory, aListEntries, false, false );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bNeedDefaultStringIfVoidAllowed = true;
}
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
switch( nPropId )
{
case PROPERTY_ID_REPEAT_DELAY:
{
OTimeDurationControl* pControl = new OTimeDurationControl( impl_getDefaultDialogParent_nothrow(), WB_BORDER | WB_TABSTOP );
aDescriptor.Control = pControl;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
pControl->setMinValue( Optional< double >( sal_True, 0 ) );
pControl->setMaxValue( Optional< double >( sal_True, ::std::numeric_limits< double >::max() ) );
}
break;
case PROPERTY_ID_TABINDEX:
case PROPERTY_ID_BOUNDCOLUMN:
case PROPERTY_ID_VISIBLESIZE:
case PROPERTY_ID_MAXTEXTLEN:
case PROPERTY_ID_LINEINCREMENT:
case PROPERTY_ID_BLOCKINCREMENT:
case PROPERTY_ID_SPININCREMENT:
{
Optional< double > aMinValue( sal_True, 0 );
Optional< double > aMaxValue( sal_True, 0x7FFFFFFF );
if ( nPropId == PROPERTY_ID_MAXTEXTLEN || nPropId == PROPERTY_ID_BOUNDCOLUMN )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
aMinValue.Value = -1;
else if ( nPropId == PROPERTY_ID_VISIBLESIZE )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
aMinValue.Value = 1;
else
aMinValue.Value = 0;
aDescriptor.Control = PropertyHandlerHelper::createNumericControl(
_rxControlFactory, 0, aMinValue, aMaxValue, false );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
case PROPERTY_ID_DECIMAL_ACCURACY:
{
Optional< double > aMinValue( sal_True, 0 );
Optional< double > aMaxValue( sal_True, 20 );
aDescriptor.Control = PropertyHandlerHelper::createNumericControl(
_rxControlFactory, 0, aMinValue, aMaxValue, false );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// DataSource
case PROPERTY_ID_DATASOURCE:
{
aDescriptor.PrimaryButtonId = UID_PROP_DLG_ATTR_DATASOURCE;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
::std::vector< OUString > aListEntries;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Reference< XDatabaseContext > xDatabaseContext = sdb::DatabaseContext::create( m_xContext );
Sequence< OUString > aDatasources = xDatabaseContext->getElementNames();
aListEntries.resize( aDatasources.getLength() );
::std::copy( aDatasources.begin(), aDatasources.end(), aListEntries.begin() );
aDescriptor.Control = PropertyHandlerHelper::createComboBoxControl(
_rxControlFactory, aListEntries, false, true );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
case PROPERTY_ID_CONTROLSOURCE:
{
::std::vector< OUString > aFieldNames;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
impl_initFieldList_nothrow( aFieldNames );
aDescriptor.Control = PropertyHandlerHelper::createComboBoxControl(
_rxControlFactory, aFieldNames, false, false );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
case PROPERTY_ID_COMMAND:
impl_describeCursorSource_nothrow( aDescriptor, _rxControlFactory );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
case PROPERTY_ID_LISTSOURCE:
impl_describeListSourceUI_throw( aDescriptor, _rxControlFactory );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
}
if ( !aDescriptor.Control.is() )
aDescriptor.Control = _rxControlFactory->createPropertyControl( nControlType, bReadOnly );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( ( aProperty.Attributes & PropertyAttribute::MAYBEVOID ) != 0 )
{
// insert the string "Default" string, if necessary
if ( bNeedDefaultStringIfVoidAllowed || ( nControlType == PropertyControlType::ColorListBox ) )
{
Reference< XStringListControl > xStringList( aDescriptor.Control, UNO_QUERY_THROW );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
xStringList->prependListEntry( m_sDefaultValueString );
m_aPropertiesWithDefListEntry.insert( _rPropertyName );
}
}
if ( !aDescriptor.PrimaryButtonId.isEmpty() )
aDescriptor.HasPrimaryButton = sal_True;
if ( !aDescriptor.SecondaryButtonId.isEmpty() )
aDescriptor.HasSecondaryButton = sal_True;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool bIsDataProperty = ( nPropertyUIFlags & PROP_FLAG_DATA_PROPERTY ) != 0;
aDescriptor.Category = bIsDataProperty ? OUString("Data") : OUString("General");
return aDescriptor;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
InteractiveSelectionResult SAL_CALL FormComponentPropertyHandler::onInteractivePropertySelection( const OUString& _rPropertyName, sal_Bool /*_bPrimary*/, Any& _rData, const Reference< XObjectInspectorUI >& _rxInspectorUI ) throw (UnknownPropertyException, NullPointerException, RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
if ( !_rxInspectorUI.is() )
throw NullPointerException();
::osl::ClearableMutexGuard aGuard( m_aMutex );
PropertyId nPropId( impl_getPropertyId_throwUnknownProperty( _rPropertyName ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
InteractiveSelectionResult eResult = InteractiveSelectionResult_Cancelled;
switch ( nPropId )
{
case PROPERTY_ID_DEFAULT_SELECT_SEQ:
case PROPERTY_ID_SELECTEDITEMS:
if ( impl_dialogListSelection_nothrow( _rPropertyName, aGuard ) )
eResult = InteractiveSelectionResult_Success;
break;
case PROPERTY_ID_FILTER:
case PROPERTY_ID_SORT:
{
OUString sClause;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( impl_dialogFilterOrSort_nothrow( PROPERTY_ID_FILTER == nPropId, sClause, aGuard ) )
{
_rData <<= sClause;
eResult = InteractiveSelectionResult_ObtainedValue;
}
}
break;
case PROPERTY_ID_MASTERFIELDS:
case PROPERTY_ID_DETAILFIELDS:
if ( impl_dialogLinkedFormFields_nothrow( aGuard ) )
eResult = InteractiveSelectionResult_Success;
break;
case PROPERTY_ID_FORMATKEY:
if ( impl_dialogFormatting_nothrow( _rData, aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue;
break;
case PROPERTY_ID_IMAGE_URL:
if ( impl_browseForImage_nothrow( _rData, aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue;
break;
case PROPERTY_ID_TARGET_URL:
if ( impl_browseForTargetURL_nothrow( _rData, aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue;
break;
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
case PROPERTY_ID_FONT:
if ( impl_executeFontDialog_nothrow( _rData, aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
case PROPERTY_ID_DATASOURCE:
if ( impl_browseForDatabaseDocument_throw( _rData, aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue;
break;
case PROPERTY_ID_BACKGROUNDCOLOR:
case PROPERTY_ID_FILLCOLOR:
case PROPERTY_ID_SYMBOLCOLOR:
case PROPERTY_ID_BORDERCOLOR:
if ( impl_dialogColorChooser_throw( nPropId, _rData, aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue;
break;
case PROPERTY_ID_CONTROLLABEL:
if ( impl_dialogChooseLabelControl_nothrow( _rData, aGuard ) )
eResult = InteractiveSelectionResult_ObtainedValue;
break;
case PROPERTY_ID_TABINDEX:
if ( impl_dialogChangeTabOrder_nothrow( aGuard ) )
eResult = InteractiveSelectionResult_Success;
break;
case PROPERTY_ID_COMMAND:
case PROPERTY_ID_LISTSOURCE:
if ( impl_doDesignSQLCommand_nothrow( _rxInspectorUI, nPropId ) )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
eResult = InteractiveSelectionResult_Pending;
break;
default:
2011-03-01 17:55:09 +01:00
OSL_FAIL( "FormComponentPropertyHandler::onInteractivePropertySelection: request for a property which does not have dedicated UI!" );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
}
return eResult;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
namespace
{
void lcl_rebuildAndResetCommand( const Reference< XObjectInspectorUI >& _rxInspectorUI, const Reference< XPropertyHandler >& _rxHandler )
{
OSL_PRECOND( _rxInspectorUI.is(), "lcl_rebuildAndResetCommand: invalid BrowserUI!" );
OSL_PRECOND( _rxHandler.is(), "lcl_rebuildAndResetCommand: invalid handler!" );
_rxInspectorUI->rebuildPropertyUI( PROPERTY_COMMAND );
_rxHandler->setPropertyValue( PROPERTY_COMMAND, makeAny( OUString() ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
void SAL_CALL FormComponentPropertyHandler::actuatingPropertyChanged( const OUString& _rActuatingPropertyName, const Any& _rNewValue, const Any& /*_rOldValue*/, const Reference< XObjectInspectorUI >& _rxInspectorUI, sal_Bool _bFirstTimeInit ) throw (NullPointerException, RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
if ( !_rxInspectorUI.is() )
throw NullPointerException();
::osl::MutexGuard aGuard( m_aMutex );
PropertyId nActuatingPropId( impl_getPropertyId_nothrow( _rActuatingPropertyName ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
::std::vector< PropertyId > aDependentProperties;
switch ( nActuatingPropId )
{
// ----- EscapeProcessing -----
case PROPERTY_ID_ESCAPE_PROCESSING:
aDependentProperties.push_back( PROPERTY_ID_FILTER );
aDependentProperties.push_back( PROPERTY_ID_SORT );
break; // case PROPERTY_ID_ESCAPE_PROCESSING
// ----- CommandType -----
case PROPERTY_ID_COMMANDTYPE:
// available commands (tables or queries) might have changed
if ( !_bFirstTimeInit && m_bHaveCommand )
lcl_rebuildAndResetCommand( _rxInspectorUI, this );
aDependentProperties.push_back( PROPERTY_ID_COMMAND );
break; // case PROPERTY_ID_COMMANDTYPE
// ----- DataSourceName -----
case PROPERTY_ID_DATASOURCE:
// reset the connection, now that we have a new data source
impl_clearRowsetConnection_nothrow();
// available list source values (tables or queries) might have changed
if ( !_bFirstTimeInit && m_bHaveListSource )
_rxInspectorUI->rebuildPropertyUI( PROPERTY_LISTSOURCE );
// available commands (tables or queries) might have changed
if ( !_bFirstTimeInit && m_bHaveCommand )
lcl_rebuildAndResetCommand( _rxInspectorUI, this );
// Command also depends on DataSource
aDependentProperties.push_back( PROPERTY_ID_COMMAND );
// NO break!
// ----- Command -----
case PROPERTY_ID_COMMAND:
aDependentProperties.push_back( PROPERTY_ID_FILTER );
aDependentProperties.push_back( PROPERTY_ID_SORT );
if ( m_bComponentIsSubForm )
aDependentProperties.push_back( PROPERTY_ID_DETAILFIELDS );
break;
// ----- ListSourceType -----
case PROPERTY_ID_LISTSOURCETYPE:
if ( !_bFirstTimeInit && m_bHaveListSource )
// available list source values (tables or queries) might have changed
_rxInspectorUI->rebuildPropertyUI( PROPERTY_LISTSOURCE );
aDependentProperties.push_back( PROPERTY_ID_STRINGITEMLIST );
aDependentProperties.push_back( PROPERTY_ID_BOUNDCOLUMN );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// NO break!
// ----- StringItemList -----
case PROPERTY_ID_STRINGITEMLIST:
aDependentProperties.push_back( PROPERTY_ID_SELECTEDITEMS );
aDependentProperties.push_back( PROPERTY_ID_DEFAULT_SELECT_SEQ );
break;
// ----- ListSource -----
case PROPERTY_ID_LISTSOURCE:
aDependentProperties.push_back( PROPERTY_ID_STRINGITEMLIST );
break;
// ----- DataField -----
case PROPERTY_ID_CONTROLSOURCE:
{
OUString sControlSource;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
_rNewValue >>= sControlSource;
if ( impl_componentHasProperty_throw( PROPERTY_FILTERPROPOSAL ) )
_rxInspectorUI->enablePropertyUI( PROPERTY_FILTERPROPOSAL, !sControlSource.isEmpty() );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( impl_componentHasProperty_throw( PROPERTY_EMPTY_IS_NULL ) )
_rxInspectorUI->enablePropertyUI( PROPERTY_EMPTY_IS_NULL, !sControlSource.isEmpty() );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
aDependentProperties.push_back( PROPERTY_ID_BOUNDCOLUMN );
aDependentProperties.push_back( PROPERTY_ID_SCALEIMAGE );
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
aDependentProperties.push_back( PROPERTY_ID_SCALE_MODE );
aDependentProperties.push_back( PROPERTY_ID_INPUT_REQUIRED );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
case PROPERTY_ID_EMPTY_IS_NULL:
aDependentProperties.push_back( PROPERTY_ID_INPUT_REQUIRED );
break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// ----- SubmitEncoding -----
case PROPERTY_ID_SUBMIT_ENCODING:
{
FormSubmitEncoding eEncoding = FormSubmitEncoding_URL;
OSL_VERIFY( _rNewValue >>= eEncoding );
_rxInspectorUI->enablePropertyUI( PROPERTY_SUBMIT_METHOD, eEncoding == FormSubmitEncoding_URL );
}
break;
// ----- Repeat -----
case PROPERTY_ID_REPEAT:
{
bool bIsRepeating = false;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( _rNewValue >>= bIsRepeating );
_rxInspectorUI->enablePropertyUI( PROPERTY_REPEAT_DELAY, bIsRepeating );
}
break;
// ----- TabStop -----
case PROPERTY_ID_TABSTOP:
{
if ( !impl_componentHasProperty_throw( PROPERTY_TABINDEX ) )
break;
bool bHasTabStop = false;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
_rNewValue >>= bHasTabStop;
_rxInspectorUI->enablePropertyUI( PROPERTY_TABINDEX, bHasTabStop );
}
break;
// ----- Border -----
case PROPERTY_ID_BORDER:
{
sal_Int16 nBordeType = VisualEffect::NONE;
OSL_VERIFY( _rNewValue >>= nBordeType );
_rxInspectorUI->enablePropertyUI( PROPERTY_BORDERCOLOR, nBordeType == VisualEffect::FLAT );
}
break;
// ----- DropDown -----
case PROPERTY_ID_DROPDOWN:
{
if ( impl_isSupportedProperty_nothrow( PROPERTY_ID_LINECOUNT ) )
{
bool bDropDown = true;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
_rNewValue >>= bDropDown;
_rxInspectorUI->enablePropertyUI( PROPERTY_LINECOUNT, bDropDown );
}
}
break;
// ----- ImageURL -----
case PROPERTY_ID_IMAGE_URL:
{
if ( impl_isSupportedProperty_nothrow( PROPERTY_ID_IMAGEPOSITION ) )
{
OUString sImageURL;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( _rNewValue >>= sImageURL );
_rxInspectorUI->enablePropertyUI( PROPERTY_IMAGEPOSITION, !sImageURL.isEmpty() );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
aDependentProperties.push_back( PROPERTY_ID_SCALEIMAGE );
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
aDependentProperties.push_back( PROPERTY_ID_SCALE_MODE );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
// ----- ButtonType -----
case PROPERTY_ID_BUTTONTYPE:
{
FormButtonType eButtonType( FormButtonType_PUSH );
OSL_VERIFY( _rNewValue >>= eButtonType );
_rxInspectorUI->enablePropertyUI( PROPERTY_TARGET_URL, FormButtonType_URL == eButtonType );
}
// NO break!
// ----- TargetURL -----
case PROPERTY_ID_TARGET_URL:
aDependentProperties.push_back( PROPERTY_ID_TARGET_FRAME );
break; // case PROPERTY_ID_TARGET_URL
// ----- TriState -----
case PROPERTY_ID_TRISTATE:
if ( !_bFirstTimeInit )
_rxInspectorUI->rebuildPropertyUI( m_eComponentClass == eFormControl ? OUString(PROPERTY_DEFAULT_STATE) : OUString(PROPERTY_STATE) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break; // case PROPERTY_ID_TRISTATE
// ----- DecimalAccuracy -----
case PROPERTY_ID_DECIMAL_ACCURACY:
// ----- ShowThousandsSeparator -----
case PROPERTY_ID_SHOWTHOUSANDSEP:
{
bool bAccuracy = (PROPERTY_ID_DECIMAL_ACCURACY == nActuatingPropId);
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
sal_uInt16 nNewDigits = 0;
bool bUseSep = false;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( bAccuracy )
OSL_VERIFY( _rNewValue >>= nNewDigits );
else
OSL_VERIFY( _rNewValue >>= bUseSep );
// propagate the changes to the min/max/default fields
OUString aAffectedProps[] = { OUString(PROPERTY_VALUE), OUString(PROPERTY_DEFAULT_VALUE), OUString(PROPERTY_VALUEMIN), OUString(PROPERTY_VALUEMAX) };
2010-10-15 18:15:35 +01:00
for (sal_uInt16 i=0; i<SAL_N_ELEMENTS(aAffectedProps); ++i)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
Reference< XPropertyControl > xControl;
try
{
xControl = _rxInspectorUI->getPropertyControl( aAffectedProps[i] );
}
2011-12-10 22:14:57 +09:00
catch( const UnknownPropertyException& ) {}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( xControl.is() )
{
OFormattedNumericControl* pControl = dynamic_cast< OFormattedNumericControl* >( xControl.get() );
DBG_ASSERT( pControl, "FormComponentPropertyHandler::actuatingPropertyChanged: invalid control!" );
if ( pControl )
CWS-TOOLING: integrate CWS cmcfixes51 2008-12-08 10:12:55 +0100 cmc r264975 : #i96203# protect with ifdefs to avoid unused symbol on mac 2008-12-05 12:23:47 +0100 cmc r264898 : CWS-TOOLING: rebase CWS cmcfixes51 to trunk@264807 (milestone: DEV300:m37) 2008-12-01 14:45:17 +0100 cmc r264606 : #i76655# ehlos apparently required 2008-11-28 17:49:30 +0100 cmc r264567 : #i96655# remove newly unused method 2008-11-28 10:41:28 +0100 cmc r264531 : #i96647# better ppc-bridges flushCode impl 2008-11-27 12:58:40 +0100 cmc r264478 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 12:32:49 +0100 cmc r264476 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 12:26:02 +0100 cmc r264475 : #i96655# redundant old table export helpers 2008-11-27 11:49:06 +0100 cmc r264473 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:38:35 +0100 cmc r264471 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:14:21 +0100 cmc r264467 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:06:22 +0100 cmc r264464 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:58:18 +0100 cmc r264462 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:41:44 +0100 cmc r264461 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:19:24 +0100 cmc r264460 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:13:39 +0100 cmc r264459 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:06:14 +0100 cmc r264458 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:59:54 +0100 cmc r264457 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:52:51 +0100 cmc r264456 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:48:26 +0100 cmc r264454 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:40:20 +0100 cmc r264452 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:35:26 +0100 cmc r264451 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:31:00 +0100 cmc r264450 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:24:08 +0100 cmc r264449 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:26:15 +0100 cmc r264443 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:21:01 +0100 cmc r264442 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:09:40 +0100 cmc r264441 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 23:51:56 +0100 cmc r264440 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 23:49:09 +0100 cmc r264439 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 18:09:54 +0100 cmc r264432 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 18:07:40 +0100 cmc r264431 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:28:02 +0100 cmc r264429 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:27:39 +0100 cmc r264428 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:18:36 +0100 cmc r264426 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 16:22:16 +0100 cmc r264415 : #i96624# make implicit braces and brackets explicit to avoid warnings 2008-11-26 16:00:23 +0100 cmc r264409 : #i90426# remove warnings from svtools 2008-11-26 15:59:17 +0100 cmc r264408 : #i90426# remove warnings 2008-11-26 15:47:32 +0100 cmc r264404 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:46:57 +0100 cmc r264394 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:19:50 +0100 cmc r264387 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:15:26 +0100 cmc r264386 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:11:26 +0100 cmc r264384 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 13:44:23 +0100 cmc r264380 : #i96084# comfirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 13:12:24 +0100 cmc r264372 : #i96604# silence new warnings 2008-11-26 12:35:02 +0100 cmc r264369 : #i96203# make qstarter work in 3-layer land 2008-11-26 12:33:04 +0100 cmc r264368 : #i96170# ensure gtypes are up and running
2008-12-11 07:05:03 +00:00
{
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( bAccuracy )
pControl->SetDecimalDigits( nNewDigits );
else
pControl->SetThousandsSep( bUseSep );
CWS-TOOLING: integrate CWS cmcfixes51 2008-12-08 10:12:55 +0100 cmc r264975 : #i96203# protect with ifdefs to avoid unused symbol on mac 2008-12-05 12:23:47 +0100 cmc r264898 : CWS-TOOLING: rebase CWS cmcfixes51 to trunk@264807 (milestone: DEV300:m37) 2008-12-01 14:45:17 +0100 cmc r264606 : #i76655# ehlos apparently required 2008-11-28 17:49:30 +0100 cmc r264567 : #i96655# remove newly unused method 2008-11-28 10:41:28 +0100 cmc r264531 : #i96647# better ppc-bridges flushCode impl 2008-11-27 12:58:40 +0100 cmc r264478 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 12:32:49 +0100 cmc r264476 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 12:26:02 +0100 cmc r264475 : #i96655# redundant old table export helpers 2008-11-27 11:49:06 +0100 cmc r264473 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:38:35 +0100 cmc r264471 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:14:21 +0100 cmc r264467 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 11:06:22 +0100 cmc r264464 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:58:18 +0100 cmc r264462 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:41:44 +0100 cmc r264461 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:19:24 +0100 cmc r264460 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:13:39 +0100 cmc r264459 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 10:06:14 +0100 cmc r264458 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:59:54 +0100 cmc r264457 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:52:51 +0100 cmc r264456 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:48:26 +0100 cmc r264454 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:40:20 +0100 cmc r264452 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:35:26 +0100 cmc r264451 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:31:00 +0100 cmc r264450 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 09:24:08 +0100 cmc r264449 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:26:15 +0100 cmc r264443 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:21:01 +0100 cmc r264442 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-27 00:09:40 +0100 cmc r264441 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 23:51:56 +0100 cmc r264440 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 23:49:09 +0100 cmc r264439 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 18:09:54 +0100 cmc r264432 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 18:07:40 +0100 cmc r264431 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:28:02 +0100 cmc r264429 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:27:39 +0100 cmc r264428 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 17:18:36 +0100 cmc r264426 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 16:22:16 +0100 cmc r264415 : #i96624# make implicit braces and brackets explicit to avoid warnings 2008-11-26 16:00:23 +0100 cmc r264409 : #i90426# remove warnings from svtools 2008-11-26 15:59:17 +0100 cmc r264408 : #i90426# remove warnings 2008-11-26 15:47:32 +0100 cmc r264404 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:46:57 +0100 cmc r264394 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:19:50 +0100 cmc r264387 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:15:26 +0100 cmc r264386 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 14:11:26 +0100 cmc r264384 : #i96084# confirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 13:44:23 +0100 cmc r264380 : #i96084# comfirm existing logic with explicit brackets to remove new gcc warnings 2008-11-26 13:12:24 +0100 cmc r264372 : #i96604# silence new warnings 2008-11-26 12:35:02 +0100 cmc r264369 : #i96203# make qstarter work in 3-layer land 2008-11-26 12:33:04 +0100 cmc r264368 : #i96170# ensure gtypes are up and running
2008-12-11 07:05:03 +00:00
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
}
break;
// ----- FormatKey -----
case PROPERTY_ID_FORMATKEY:
{
FormatDescription aNewDesc;
Reference< XNumberFormatsSupplier > xSupplier;
OSL_VERIFY( m_xComponent->getPropertyValue( PROPERTY_FORMATSSUPPLIER ) >>= xSupplier );
Reference< XUnoTunnel > xTunnel( xSupplier, UNO_QUERY );
DBG_ASSERT(xTunnel.is(), "FormComponentPropertyHandler::actuatingPropertyChanged: xTunnel is invalid!");
if ( xTunnel.is() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
SvNumberFormatsSupplierObj* pSupplier = reinterpret_cast<SvNumberFormatsSupplierObj*>(xTunnel->getSomething(SvNumberFormatsSupplierObj::getUnoTunnelId()));
// the same again
aNewDesc.pSupplier = pSupplier;
if ( !( _rNewValue >>= aNewDesc.nKey ) )
aNewDesc.nKey = 0;
// give each control which has to know this an own copy of the description
OUString aFormattedPropertyControls[] = {
OUString(PROPERTY_EFFECTIVE_MIN), OUString(PROPERTY_EFFECTIVE_MAX), OUString(PROPERTY_EFFECTIVE_DEFAULT), OUString(PROPERTY_EFFECTIVE_VALUE)
};
2010-10-15 18:15:35 +01:00
for ( sal_uInt16 i=0; i<SAL_N_ELEMENTS(aFormattedPropertyControls); ++i )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
Reference< XPropertyControl > xControl;
try
{
xControl = _rxInspectorUI->getPropertyControl( aFormattedPropertyControls[i] );
}
2011-12-10 22:14:57 +09:00
catch( const UnknownPropertyException& ) {}
if ( xControl.is() )
{
OFormattedNumericControl* pControl = dynamic_cast< OFormattedNumericControl* >( xControl.get() );
DBG_ASSERT( pControl, "FormComponentPropertyHandler::actuatingPropertyChanged: invalid control!" );
if ( pControl )
pControl->SetFormatDescription( aNewDesc );
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
}
break;
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
case PROPERTY_ID_TOGGLE:
{
bool bIsToggleButton = false;
CWS-TOOLING: integrate CWS dba32b 2009-06-03 14:58:08 +0200 fs r272581 : #i102439# 2009-05-29 13:56:18 +0200 fs r272456 : remove the sub form when the 'add subform' setting changes from <true/> to <false/>, not only its controls 2009-05-29 13:19:27 +0200 fs r272454 : display '(Default)' instead of an empty string when a control has the default font 2009-05-28 20:49:18 +0200 fs r272428 : #i98162# getFirstSelectedValue: do not return reference to a temporary 2009-05-27 15:30:22 +0200 msc r272353 : #102303# 2009-05-26 13:03:06 +0200 fs r272295 : spelling 2009-05-26 12:59:54 +0200 fs r272294 : merge m48 version to get latest cygwin related fixes 2009-05-25 14:02:06 +0200 fs r272239 : remove references to local files, needed for debugging sessions only 2009-05-25 14:01:16 +0200 fs r272238 : #i102021# ensure members such as bNumberFormat are initialized before actually returning them 2009-05-25 13:10:20 +0200 fs r272236 : #i10000# reset ENABLE_EVOAB2 2009-05-22 06:44:45 +0200 oj r272167 : #i99104# add import handler for calc-sett 2009-05-22 06:42:27 +0200 oj r272166 : #i99104# impl NullDate as member 2009-05-22 06:36:22 +0200 oj r272165 : #i99104# handle nulldate from parent model 2009-05-22 06:33:13 +0200 oj r272164 : #i99104# export and import calculation-settings and nulldate 2009-05-22 06:27:50 +0200 oj r272163 : #i99104# export and import calculation-settings and nulldate 2009-05-20 13:29:58 +0200 oj r272118 : #i99911# handle invalid name 2009-05-20 13:28:49 +0200 oj r272117 : #i101261# handle different rowsets 2009-05-20 11:29:55 +0200 msc r272111 : #i100000# 2009-05-20 11:28:27 +0200 msc r272110 : merge in change from dba32a 2009-05-20 11:27:38 +0200 msc r272109 : #102082# CTRL + C does not work 2009-05-20 09:43:36 +0200 oj r272106 : clean up includes 2009-05-20 09:32:15 +0200 oj r272105 : #i99060# merge error resovled now VERTICAL_ALIGN is in both stmt 2009-05-20 08:37:21 +0200 msc r272104 : add workaround for issue #102010# 2009-05-20 08:10:12 +0200 oj r272103 : #i99104# use numberformatkey 2009-05-20 08:07:02 +0200 oj r272102 : #i99104# use column info from rowset 2009-05-20 08:04:43 +0200 oj r272101 : #i102032# use a special column type where prec and scale are the values currently set at the column 2009-05-20 08:03:04 +0200 oj r272100 : #i102032# correct type info, we have to use SQL defined type names 2009-05-19 10:27:02 +0200 oj r272061 : #i99104# export null-date 2009-05-19 08:26:53 +0200 oj r272056 : #i99104# export null-date 2009-05-18 13:15:10 +0200 msc r272014 : add issue #102019# 2009-05-18 11:33:07 +0200 msc r272005 : add issue #102019# 2009-05-18 08:59:45 +0200 msc r271996 : add workaroud for issue #102010# 2009-05-15 10:21:24 +0200 msc r271929 : #101944# 2009-05-11 21:18:30 +0200 fs r271792 : #i99914# 2009-05-08 13:52:06 +0200 oj r271715 : #i96423# remember column span 2009-05-08 11:26:19 +0200 oj r271708 : #i98605# impl new scale mode 2009-05-08 10:33:35 +0200 fs r271706 : SendUserCall: only call into the shape notification routine for UserCall types where this is necessary (performance issue) 2009-05-07 20:52:44 +0200 fs r271698 : outsource ShapeProperty from shapepropertynotifier.hxx 2009-05-07 20:43:33 +0200 fs r271697 : #i99056# use notifyShapePropertyChange, instead of getShapePropertyChangeNotifier - the latter throws if no shape exists, yet 2009-05-07 20:33:58 +0200 fs r271696 : #i99056# +notifyShapePropertyChange: allow notifying chages without checking whether there actually already exists an SvxShape 2009-05-07 16:22:15 +0200 fs r271679 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:21:37 +0200 fs r271678 : #i10000# cygwin needs quotes around the classpath 2009-05-07 16:01:11 +0200 oj r271677 : #i99914# notify parent handler 2009-05-07 15:54:54 +0200 fs r271676 : #i10000# cygwin needs some quoting 2009-05-07 14:49:48 +0200 oj r271672 : #i99277# quote alias name 2009-05-07 14:48:12 +0200 oj r271671 : #i92538# add ~ in front of type 2009-05-07 14:37:13 +0200 oj r271667 : #i99118# change type from char to varchar 2009-05-07 14:36:23 +0200 oj r271666 : #i99118# clear dest columns when changing to create new table 2009-05-07 13:35:32 +0200 oj r271657 : #i94467# handle type 0 as double as well 2009-05-07 13:20:49 +0200 oj r271655 : i99743# setNull when varchar is no text 2009-05-07 12:58:06 +0200 fs r271651 : initialize the SdrObject's property change notifier after the ctor, if necessary 2009-05-07 11:47:18 +0200 fs r271647 : #i10000# 2009-05-07 10:57:16 +0200 fs r271639 : OPropertyBrowserController::propertyChange: care for the current property state, too, and properly forward it to the UI 2009-05-07 10:18:14 +0200 fs r271636 : onNewComponent: do not ask the map for grid columns, it will throw 2009-05-07 10:09:55 +0200 fs r271634 : #i101623# 2009-05-07 09:53:44 +0200 fs r271631 : #i101622# 2009-05-06 21:55:53 +0200 fs r271615 : #i10000# 2009-05-06 21:10:42 +0200 fs r271611 : #i10000# 2009-05-06 13:11:48 +0200 fs r271583 : #i10000# 2009-05-05 22:29:31 +0200 fs r271559 : proper assertion message 2009-05-05 22:29:03 +0200 fs r271558 : diagnostics 2009-05-05 22:16:16 +0200 fs r271557 : #i10000# 2009-05-05 13:50:32 +0200 fs r271513 : #i10000# 2009-05-05 10:21:50 +0200 fs r271503 : #i10000# 2009-05-05 09:30:26 +0200 fs r271501 : why did those survive the rebase -C step? 2009-05-05 09:18:12 +0200 fs r271500 : #i10000# 2009-05-04 17:08:17 +0200 fs r271475 : CWS-TOOLING: rebase CWS dba32b to trunk@271427 (milestone: DEV300:m47) 2009-05-04 14:51:26 +0200 fs r271456 : line ends 2009-04-30 15:55:27 +0200 fs r271418 : NewURL -> PublicConnectionURL 2009-04-22 21:18:34 +0200 fs r271141 : #i100944# 2009-04-22 09:12:26 +0200 oj r271071 : #i101261# little code change 2009-04-22 09:11:43 +0200 oj r271070 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:11:25 +0200 oj r271069 : #i101261# new grabage container for nodes 2009-04-22 09:11:02 +0200 oj r271068 : #i101261# new grabage container for nodes 2009-04-22 09:10:44 +0200 oj r271067 : #i101261# new grabage container for nodes 2009-04-22 09:10:21 +0200 oj r271066 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:08:24 +0200 oj r271065 : #i101261# only ask for parameters which aren't set before 2009-04-22 09:07:25 +0200 oj r271064 : #i101261# only ask for parameters which aren't set before 2009-04-22 08:49:07 +0200 oj r271062 : #i77501# preview only when needed 2009-04-22 08:45:44 +0200 oj r271061 : #i101261# new prop max rows 2009-04-22 08:44:18 +0200 oj r271060 : #i101261# create dataprovider earlier to avoid the wrong legend in chart 2009-04-22 08:42:48 +0200 oj r271059 : #i101261# handle parameter 2009-04-17 21:00:23 +0200 fs r270954 : #i98350# 2009-04-17 13:54:19 +0200 fs r270942 : #i99565# 2009-04-17 13:51:34 +0200 fs r270940 : #i101153# only localize the (potentially) localizable properties when there really is support at the control model 2009-04-17 11:43:14 +0200 fs r270932 : removed superfluous include 2009-04-17 10:10:15 +0200 fs r270926 : #i10000# 2009-04-17 10:02:36 +0200 fs r270925 : #i10000# 2009-04-17 09:15:13 +0200 fs r270918 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:14:56 +0200 fs r270917 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 09:13:25 +0200 fs r270915 : #i99056# some more refactoring of the recently introduced property change notification mechanism for UNO shapes 2009-04-17 08:30:34 +0200 fs r270914 : removed unotools/servicehelper.hxx in favour of the (duplicated) comphelper/servicehelper.hxx 2009-04-16 21:05:25 +0200 fs r270903 : #i10000# 2009-04-16 20:43:43 +0200 fs r270902 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-16 15:57:36 +0200 fs r270891 : #i99056# make SetUnoControlModel virtual 2009-04-16 15:44:02 +0200 fs r270890 : #i99056# let the ScShapeObj notify changes in its Anchor property 2009-04-16 15:36:47 +0200 fs r270889 : #i99056# enable the sheet anchor type property, too 2009-04-16 15:33:45 +0200 fs r270887 : #i99056# shape notification outsourced to the SdrObject, this is what all other shape implementations (which only aggregate an SvxShape) have access to, too 2009-04-15 14:53:13 +0200 fs r270844 : #i10000# 2009-04-15 13:08:29 +0200 fs r270836 : #i10000# 2009-04-15 12:28:14 +0200 fs r270832 : #i10000# 2009-04-15 10:59:14 +0200 fs r270827 : #i10000# 2009-04-15 09:41:08 +0200 oj r270823 : fix issues found with findbugs and pmd 2009-04-14 21:08:04 +0200 fs r270808 : #i99056# implement SheetAnchorType - now the only thing missing to enable it is the proper notification when it is modified 2009-04-14 17:09:00 +0200 fs r270799 : #i99056# implement XServiceInfo for the ScShapeObj 2009-04-14 17:07:55 +0200 fs r270798 : #i99056# implement TextAnchorType, partially implement SheetAnchorType 2009-04-14 15:54:05 +0200 fs r270786 : #i99056# SwXShape: notify changes of the AnchorType property 2009-04-14 15:47:32 +0200 fs r270785 : #i99056# deliver shapepropertynotifier.hxx 2009-04-14 15:46:54 +0200 fs r270784 : diagnostics 2009-04-14 15:08:28 +0200 fs r270781 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:41:09 +0200 fs r270773 : #i99056# outsourced the SvxShape's property change notification code into a dedicated class 2009-04-14 14:37:23 +0200 fs r270772 : in dtor, remove the properties from the temporary component context 2009-04-14 14:36:34 +0200 fs r270771 : getWeakUnoShape made const 2009-04-14 12:23:08 +0200 oj r270757 : #i101064# add missing braces 2009-04-14 12:21:25 +0200 oj r270756 : #i101065# add braces for gcc 4.3.2 2009-04-14 12:17:45 +0200 oj r270755 : #i101059# add dep for manifest 2009-04-09 12:06:58 +0200 oj r270686 : #i93100# use OptimalSize from control to get height 2009-04-08 09:56:55 +0200 oj r270619 : #i92537# handle calculations in the select columns as well 2009-04-08 09:30:39 +0200 oj r270615 : #i96657# throw error message when the key doesn't have any columns 2009-04-07 12:08:26 +0200 oj r270592 : #i77501# impl preview of the executed report 2009-04-07 12:01:56 +0200 oj r270591 : #i77501# impl preview of the executed report 2009-04-07 11:41:03 +0200 oj r270590 : #i77501# impl preview of the executed report 2009-04-07 11:39:32 +0200 oj r270589 : #i77501# impl preview of the executed report 2009-04-07 11:29:25 +0200 oj r270588 : #i77501# convert dos to unix lineends 2009-04-07 11:28:23 +0200 oj r270587 : #i77501# impl preview of the executed report 2009-04-07 11:16:50 +0200 oj r270586 : #i77501# impl preview of the executed report 2009-04-07 11:16:00 +0200 oj r270585 : #i77501# impl preview of the executed report 2009-04-07 11:15:44 +0200 oj r270584 : #i77501# impl preview of the executed report 2009-04-07 11:15:28 +0200 oj r270583 : #i77501# impl preview of the executed report 2009-04-07 11:15:04 +0200 oj r270582 : #i77501# impl preview of the executed report 2009-04-06 15:38:54 +0200 fs r270559 : merge changes from CWS dba32a herein 2009-04-03 15:56:16 +0200 fs r270494 : ImpSvMEdit::Resize: do multiple iterations, if necessary 2009-04-03 14:35:49 +0200 fs r270487 : #i10000# 2009-04-03 13:17:16 +0200 fs r270476 : #i99056# display geometry information for controls, too 2009-04-03 13:16:37 +0200 fs r270475 : #i99056# better ordering of the geometry properties 2009-04-03 13:16:07 +0200 fs r270473 : #i99056# now that SvxShape supports property change listeners, forward add/remove requests to it 2009-04-03 13:13:18 +0200 fs r270472 : #i99056# at SvxShape, allow for PropertyChangeListeners for Size/Position 2009-04-03 09:29:27 +0200 oj r270456 : #i94571# use correct prop name 2009-04-03 09:14:54 +0200 fs r270451 : merge changes from CWS dba32a herein 2009-04-02 17:00:51 +0200 fs r270424 : better diagnostics 2009-04-02 16:35:19 +0200 fs r270421 : diagnostics 2009-04-02 16:34:50 +0200 fs r270420 : #i99056# mxUnoShape not accessible anymore, use impl_setUnoShape instead 2009-04-02 16:32:48 +0200 fs r270419 : #i99056# make getUnoShape cheaper: keep the pointer to the SvxShape all the time, so there's no need to ask for it in getUnoShape. As a consequence, we will later be able to use the pointer in scenarious where performance (potentially) matters 2009-04-02 16:31:13 +0200 fs r270417 : merge changes from CWS dba32a herein 2009-04-02 16:23:16 +0200 fs r270414 : merge changes from CWS dba32a herein 2009-04-02 14:10:35 +0200 fs r270405 : #i10000# 2009-04-02 14:06:26 +0200 fs r270404 : merge changes from CWS dba32a herein 2009-04-02 14:03:03 +0200 fs r270401 : #i10000# 2009-04-02 13:58:13 +0200 fs r270400 : #i10000# 2009-04-02 12:59:44 +0200 fs r270397 : merge changes from CWS dba32a herein 2009-04-02 12:46:30 +0200 fs r270396 : #i99056# let the form page maintain a mapping between control models and control shapes 2009-04-02 12:44:07 +0200 fs r270395 : merge changes from CWS dba32a herein 2009-04-02 12:42:06 +0200 fs r270394 : merge changes from CWS dba32a herein 2009-04-02 12:35:20 +0200 fs r270393 : #i10000# precompiled header 2009-04-02 12:05:31 +0200 fs r270392 : merge changes from CWS dba32a herein 2009-04-02 12:00:42 +0200 fs r270391 : merge changes from CWS dba32a herein 2009-04-02 11:47:26 +0200 fs r270390 : merge changes from CWS dba32a herein 2009-04-02 11:39:15 +0200 oj r270389 : #i94467# foxpro impl several new types 2009-04-02 11:35:58 +0200 fs r270387 : merge changes from CWS dba32a herein 2009-04-01 14:10:51 +0200 fs r270329 : merge changes from CWS dba32a herein 2009-03-31 17:29:50 +0200 fs r270290 : merge changes from CWS dba32a herein 2009-03-30 14:53:56 +0200 fs r270233 : #i100417# don't set grid column widths to 0, but to <void/> 2009-03-30 12:31:03 +0200 oj r270213 : #i100552# wrong orb used 2009-03-30 12:19:20 +0200 oj r270212 : #i98303# convertlike corrected to sal_Unicode 2009-03-30 11:58:25 +0200 fs r270210 : merge changes from CWS dba32a herein 2009-03-30 11:38:16 +0200 oj r270205 : remove duplicate code from merge 2009-03-30 11:02:27 +0200 fs r270202 : merge changes from CWS dba32a herein 2009-03-30 11:02:19 +0200 fs r270201 : merge changes from CWS dba32a herein 2009-03-30 10:31:26 +0200 oj r270200 : #i100665# only throw exception and do not drop table 2009-03-30 09:36:24 +0200 fs r270195 : assertion text 2009-03-28 20:21:58 +0100 fs r270187 : #ii10000# 2009-03-28 20:19:54 +0100 fs r270186 : removed unused help ids 2009-03-28 20:19:40 +0100 fs r270185 : removed unused help ids 2009-03-28 20:19:10 +0100 fs r270184 : #i100237# +DefaultState/XReset 2009-03-28 00:29:29 +0100 fs r270177 : CWS-TOOLING: rebase CWS dba32b to trunk@270033 (milestone: DEV300:m45) 2009-03-27 22:56:46 +0100 fs r270173 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:55:52 +0100 fs r270172 : #i100237# DefaultState property for buttons, enabled only when Toggle=Yes 2009-03-27 22:54:15 +0100 fs r270171 : #i100237# DEFAULT_CHECKED -> DEFAULT_STATE 2009-03-27 22:53:54 +0100 fs r270170 : #i100237# introduce a DefaultState property for buttons, which implies buttongs supporting XReset, which needed some refactoring 2009-03-27 13:31:41 +0100 fs r270152 : ignore output paths 2009-03-27 11:23:44 +0100 fs r270139 : tuned behavior with respect to invalid keys/values 2009-03-27 09:57:14 +0100 fs r270136 : don't allow Double.NaN 2009-03-27 09:56:16 +0100 fs r270135 : talk about Double.NaN 2009-03-26 12:14:30 +0100 fs r270067 : removed unused parameter 2009-03-26 12:14:02 +0100 fs r270066 : removed widening conversion when checking keys 2009-03-26 09:17:34 +0100 fs r270053 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:17:11 +0100 fs r270052 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-26 09:16:49 +0100 fs r270051 : separated the enumerator functionality into a dedicated interface, this way not burdening XMap with it 2009-03-25 21:55:20 +0100 fs r270044 : #i100541# properly calculat bNeedScrollBox 2009-03-25 12:56:17 +0100 fs r270019 : renamed the previously introduced error condition 2009-03-25 12:11:48 +0100 fs r270015 : #i100095# when the error messages contain non-trivial details (SQLState/ErrorCode), then always display the 'Details' button 2009-03-25 12:10:05 +0100 fs r270012 : renamed the previously introduced error condition 2009-03-25 12:01:04 +0100 fs r270011 : #i100095# when no address book (or respective profile) can be found, then use a dedicated ErrorCondition 2009-03-25 10:29:07 +0100 fs r270003 : add missing localization 2009-03-25 10:23:12 +0100 fs r270001 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-25 10:21:55 +0100 fs r270000 : in preparation of #i1000095#: rework the error handling, allow using css.sdb.ErrorCondition values, plus allow propagating the nsresult 2009-03-20 23:05:38 +0100 fs r269829 : XMap::getSize removed 2009-03-20 23:05:19 +0100 fs r269828 : changes as suggested by sb 2009-03-20 23:04:56 +0100 fs r269827 : enhanced documentation 2009-03-20 15:31:40 +0100 fs r269815 : changes as suggested by sb 2009-03-20 13:23:52 +0100 oj r269804 : #i92538# correct the zorder that fixedtext is infront of control 2009-03-20 12:59:38 +0100 oj r269801 : #i94571# paraadjust now supports BLOCK 2009-03-20 12:58:11 +0100 oj r269800 : #i94571# export style with data style 2009-03-20 12:57:05 +0100 oj r269799 : #i94571# text align is now paraadjust 2009-03-20 12:37:02 +0100 fs r269797 : enum keys only accepted if they have the exact type, not if they have *any* enum type 2009-03-20 12:28:31 +0100 fs r269794 : some changes requested by sb 2009-03-20 08:52:47 +0100 fs r269780 : doc 2009-03-20 07:37:31 +0100 oj r269779 : #i99913# only notifiy when values are different 2009-03-20 07:36:58 +0100 oj r269778 : #i99913# add undoenv as listener at the dataprovider 2009-03-19 22:52:52 +0100 fs r269771 : added comment 2009-03-19 22:40:06 +0100 fs r269770 : +testEnumeration 2009-03-19 22:39:41 +0100 fs r269769 : implemented enumeration, getKeySet, and getValues. Should be finished now. 2009-03-19 14:01:01 +0100 oj r269743 : #i99913# reset the modified state when selecting an object 2009-03-19 12:19:54 +0100 lla r269739 : #i72390# cleanups 2009-03-19 09:25:27 +0100 fs r269727 : #i10000# 2009-03-18 23:37:02 +0100 fs r269708 : extended checks for value type acceptance 2009-03-18 23:36:41 +0100 fs r269707 : fixed value type checks 2009-03-18 14:59:56 +0100 fs r269678 : initial complex test case for the new css.container.Map implementation 2009-03-18 14:59:24 +0100 fs r269677 : verifyExpectedException moved to base class (in complexlib), and renamed to assureException for consistency 2009-03-18 14:58:35 +0100 fs r269676 : removed unused imports 2009-03-18 14:58:03 +0100 fs r269675 : first implementation of the new css.container.Map service (not completed, yet) 2009-03-18 14:57:17 +0100 fs r269674 : base class for UNO components, freeing you from some repeating work 2009-03-18 14:55:53 +0100 fs r269672 : +assureException: call a given method with given parameters on a given object, ensure that a given exception is thrown by the method implementation 2009-03-18 14:54:58 +0100 fs r269671 : +getComponentContext 2009-03-18 14:54:00 +0100 fs r269670 : isEmpty returns a boolean, not a long 2009-03-18 14:14:43 +0100 oj r269663 : #i99743# now text also supports null 2009-03-18 13:54:14 +0100 oj r269660 : #i99223# remove check for 2 params 2009-03-18 13:33:35 +0100 oj r269659 : #i99060# replace text::ParagraphVertAlign with style::VerticalAlignment 2009-03-18 13:32:18 +0100 oj r269658 : #i99060# don't set void property when void isn't allowed 2009-03-18 13:31:11 +0100 oj r269657 : #i99060# handle vertical alignment 2009-03-18 13:28:28 +0100 oj r269656 : #i99060# remove unused elements from sytle 2009-03-18 09:35:42 +0100 lla r269639 : #i72390# cleanups 2009-03-18 09:31:20 +0100 lla r269638 : #i72390# add ButtonList 2009-03-18 09:30:46 +0100 lla r269637 : #i72390# renamed interface 2009-03-18 09:30:15 +0100 lla r269636 : #i72390# use ButtonList instead of ImageList 2009-03-18 09:29:05 +0100 lla r269635 : #i72390# new ButtonList, cleanups 2009-03-18 09:26:34 +0100 lla r269634 : #i72390# cleanups 2009-03-17 12:21:20 +0100 oj r269590 : #i99222# remove assertion 2009-03-17 12:17:22 +0100 oj r269589 : #i98605# impl scale mode 2009-03-17 12:10:42 +0100 oj r269588 : #i98605# impl scale mode 2009-03-17 11:40:15 +0100 oj r269584 : #i96944# doesn't create equation for shapes 2009-03-17 11:33:16 +0100 oj r269583 : #i96423# switch calc from float to long 2009-03-16 15:19:18 +0100 fs r269550 : #i41930# enable zoom for embedded/outplace documents 2009-03-16 14:25:54 +0100 oj r269542 : #i93734# remove ContextSensitive 2009-03-16 14:21:58 +0100 oj r269541 : #i99274# page header before group header 2009-03-16 14:18:23 +0100 oj r269539 : #i99110# fix value type 2009-03-16 14:14:16 +0100 fs r269537 : line ends 2009-03-16 14:11:06 +0100 fs r269535 : line ends 2009-03-16 14:08:34 +0100 fs r269534 : #i100087# (provided my np): allow for polymorphic types with more than one parameter 2009-03-16 12:30:31 +0100 oj r269521 : compile error 2009-03-16 12:19:12 +0100 oj r269519 : compile error 2009-03-16 10:39:28 +0100 oj r269511 : compile error under linux with swap 2009-03-13 10:33:04 +0100 oj r269462 : CWS-TOOLING: rebase CWS dba32b to trunk@269297 (milestone: DEV300:m43) 2009-03-12 14:37:25 +0100 fs r269416 : interface SequenceOutputStreamTest is unneeded, and pollutes the namespace here :) 2009-03-12 14:35:07 +0100 fs r269414 : not needed 2009-03-12 14:34:15 +0100 fs r269413 : preparation for multiple tests in this module 2009-03-12 14:33:02 +0100 fs r269412 : ShowTargets was moved from module integration.forms to module complexlib 2009-03-12 14:32:48 +0100 fs r269411 : helper class for projects containing multiple complex test cases (and following a certain structure) 2009-03-12 14:00:14 +0100 fs r269407 : proper module after the move 2009-03-12 13:59:10 +0100 fs r269406 : superseded by ../makefile.mk 2009-03-12 13:47:38 +0100 fs r269403 : not needed anymore 2009-03-12 13:45:46 +0100 fs r269402 : moved, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:45:07 +0100 fs r269401 : moved from ../ 2009-03-12 13:43:59 +0100 fs r269400 : moved to ./comphelper, in preparation of adding more test cases here, with a common infrastructure 2009-03-12 13:29:47 +0100 oj r269396 : #i99914# set parent on dataprovider 2009-03-12 13:10:35 +0100 oj r269393 : #i99832# check thrown exception and show error 2009-03-12 13:08:10 +0100 fs r269392 : reorganizing tests 2009-03-12 12:52:55 +0100 oj r269390 : #i99118# convert formatkey in numberformat 2009-03-12 12:34:53 +0100 fs r269388 : new API tests 2009-03-12 12:29:05 +0100 fs r269386 : Map not yet committed 2009-03-12 12:28:36 +0100 fs r269385 : oops, forgot the SequenceInputStream during the previous refactoring 2009-03-12 12:12:39 +0100 oj r269384 : #i99104# set HasCategories prop 2009-03-12 12:12:08 +0100 oj r269383 : #i99104# check HasCategories even for internal dataprovider 2009-03-12 12:10:40 +0100 oj r269382 : #i99104# set HasCategories prop 2009-03-12 10:51:49 +0100 fs r269373 : #i10000# exception specifications 2009-03-12 10:49:18 +0100 fs r269372 : #i10000# exception specifications 2009-03-12 10:44:02 +0100 fs r269371 : #i10000# exception specifications 2009-03-12 10:30:55 +0100 fs r269368 : refactored the UNO service registration in this module, using the helper classes provided by comphelper itself, so you have less effort when extending the list of to-be-registered components 2009-03-12 10:30:37 +0100 fs r269367 : module-local includes 2009-03-12 07:05:54 +0100 oj r269357 : #i99104# database dataprovider doesn't need dataranges and diagramdata 2009-03-11 10:58:28 +0100 oj r269306 : #i99911# check if name of the report is a valid file name 2009-03-11 10:03:23 +0100 oj r269299 : #i99666# the report is new when the HierarchicalDocumentName is empty 2009-03-10 11:32:45 +0100 oj r269258 : #i99221# use fallback for language 2009-03-10 10:48:40 +0100 oj r269255 : #i99433# now use OStringBuffer 2009-03-10 10:36:21 +0100 fs r269252 : initial version of (X)Map 2009-03-10 09:52:23 +0100 oj r269246 : #i99433# now use OStringBuffer 2009-03-10 08:56:13 +0100 oj r269240 : #i99655# patch applied 2009-03-09 07:35:33 +0100 lla r269058 : #i10000# wrong variable assignment fixed 2009-03-06 17:20:40 +0100 fs r269030 : some explicit defaults 2009-03-06 17:20:30 +0100 fs r269029 : #i98600# 2009-03-06 14:40:34 +0100 fs r269009 : #i87692# during reload, prevent the document being modified just because of some control content changes ... 2009-03-06 12:52:20 +0100 lla r268997 : #i10000# ambigous problem with FontWeight fixed 2009-03-06 11:39:32 +0100 fs r268989 : #i10000# (approved by pl): use --without-t1-library configure option 2009-03-06 10:55:43 +0100 fs r268986 : #i99953# depends on xmlscript module now 2009-03-06 10:54:04 +0100 fs r268985 : #i99953# also adjust the event names found in dialogs embedded in the forms 2009-03-06 09:53:41 +0100 fs r268977 : #i10000# 2009-03-06 09:30:41 +0100 lla r268973 : #i10000# merge problems 2009-03-05 17:52:34 +0100 fs r268932 : #i98593# for sub components which are actually controlled by a DocumentDefinition (aka XComponentSupplier aka XCommandProcessor), close them by executing the 'close' command, not by suspending/closing the controller (which cannot be intercepted) 2009-03-05 11:41:56 +0100 fs r268889 : default the drop down line count for list/combo boxes to 20 2009-03-05 11:39:10 +0100 fs r268887 : do not display empty error messages 2009-03-02 10:13:57 +0100 lla r268639 : #i91541# CWS rebase m41 to m42 2009-03-02 09:06:27 +0100 lla r268635 : #i10000# add ';' to strings 2009-02-26 11:18:00 +0100 fs r268492 : reportdesign depends on REPORTBUILDER, not REPORTDESIGN 2009-02-26 10:11:38 +0100 lla r268489 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-26 09:04:11 +0100 lla r268488 : CWS-TOOLING: rebase CWS dba32b to trunk@268395 (milestone: DEV300:m42) 2009-02-24 12:09:13 +0100 lla r268392 : #i91541# #i91542# cleanups 2009-02-24 08:08:06 +0100 lla r268382 : merge all dba32a changes into dba32b 2009-02-24 07:14:55 +0100 lla r268381 : merge all dba32a changes into dba32b 2009-02-23 21:44:28 +0100 fs r268377 : oops ... don't tamper with m_aListSourceValues at the end of loadData 2009-02-23 20:57:05 +0100 fs r268376 : #i98162# don't hold the values as strings, but as ORowSetValue, this way preserving their type, and being agnostic to different result/rowset implementations doing different to-string-conversations 2009-02-23 20:55:44 +0100 fs r268375 : getObject: throwFunctionNotSupportedException, instead of silently returning NULL 2009-02-23 20:55:20 +0100 fs r268374 : #i98162# some more supported types 2009-02-23 20:54:43 +0100 fs r268373 : #i98162# +operator != 2009-02-20 09:35:39 +0100 fs r268306 : #i99422# for a font, display the font name, the style, and the size 2009-02-20 09:33:45 +0100 fs r268305 : #i99422# in the property browser, FONT supersedes CHARFONTNAME: the aggregated FormComponentHandler displays them more nicely now 2009-02-19 16:12:06 +0100 fs r268293 : #i99372# recognize DataType::FLOAT as numeric 2009-02-19 15:43:12 +0100 fs r268291 : #i99415# 2009-02-19 15:40:15 +0100 fs r268290 : #i99242# lcl_firstFocussableControl: take disabled controls into account 2009-02-19 15:34:36 +0100 fs r268289 : #i99396# properly decode the base name of the URL when using it as title 2009-02-19 15:19:05 +0100 fs r268287 : #i98247#
2009-06-05 09:47:55 +00:00
OSL_VERIFY( _rNewValue >>= bIsToggleButton );
_rxInspectorUI->enablePropertyUI( PROPERTY_DEFAULT_STATE, bIsToggleButton );
}
break;
case -1:
throw RuntimeException();
break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
default:
2011-03-01 17:55:09 +01:00
OSL_FAIL( "FormComponentPropertyHandler::actuatingPropertyChanged: did not register for this property!" );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
} // switch ( nActuatingPropId )
for ( ::std::vector< PropertyId >::const_iterator loopAffected = aDependentProperties.begin();
loopAffected != aDependentProperties.end();
++loopAffected
)
{
if ( impl_isSupportedProperty_nothrow( *loopAffected ) )
impl_updateDependentProperty_nothrow( *loopAffected, _rxInspectorUI );
}
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
void FormComponentPropertyHandler::impl_updateDependentProperty_nothrow( PropertyId _nPropId, const Reference< XObjectInspectorUI >& _rxInspectorUI ) const
{
try
{
switch ( _nPropId )
{
// ----- StringItemList -----
case PROPERTY_ID_STRINGITEMLIST:
{
ListSourceType eLSType = ListSourceType_VALUELIST;
OSL_VERIFY( impl_getPropertyValue_throw( PROPERTY_LISTSOURCETYPE ) >>= eLSType );
OUString sListSource;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
Sequence< OUString > aListSource;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Any aListSourceValue( impl_getPropertyValue_throw( PROPERTY_LISTSOURCE ) );
if ( aListSourceValue >>= aListSource )
{
if ( aListSource.getLength() )
sListSource = aListSource[0];
}
else
OSL_VERIFY( aListSourceValue >>= sListSource );
}
bool bIsEnabled = ( ( eLSType == ListSourceType_VALUELIST )
|| ( sListSource.isEmpty() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
);
_rxInspectorUI->enablePropertyUI( PROPERTY_STRINGITEMLIST, bIsEnabled );
}
break; // case PROPERTY_ID_STRINGITEMLIST
// ----- BoundColumn -----
case PROPERTY_ID_BOUNDCOLUMN:
{
ListSourceType eLSType = ListSourceType_VALUELIST;
OSL_VERIFY( impl_getPropertyValue_throw( PROPERTY_LISTSOURCETYPE ) >>= eLSType );
_rxInspectorUI->enablePropertyUI( PROPERTY_BOUNDCOLUMN,
( eLSType != ListSourceType_VALUELIST )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
);
}
break; // case PROPERTY_ID_BOUNDCOLUMN
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
// ----- ScaleImage, ScaleMode -----
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_SCALEIMAGE:
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
case PROPERTY_ID_SCALE_MODE:
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
OUString sControlSource;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( impl_isSupportedProperty_nothrow( PROPERTY_ID_CONTROLSOURCE ) )
impl_getPropertyValue_throw( PROPERTY_CONTROLSOURCE ) >>= sControlSource;
OUString sImageURL;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
impl_getPropertyValue_throw( PROPERTY_IMAGE_URL ) >>= sImageURL;
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
_rxInspectorUI->enablePropertyUI( impl_getPropertyNameFromId_nothrow( _nPropId ),
( !sControlSource.isEmpty() ) || ( !sImageURL.isEmpty() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
);
}
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
break; // case PROPERTY_ID_SCALEIMAGE, PROPERTY_ID_SCALE_MODE
// ----- InputRequired -----
case PROPERTY_ID_INPUT_REQUIRED:
{
OUString sControlSource;
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
OSL_VERIFY( impl_getPropertyValue_throw( PROPERTY_CONTROLSOURCE ) >>= sControlSource );
bool bEmptyIsNULL = false;
bool bHasEmptyIsNULL = impl_componentHasProperty_throw( PROPERTY_EMPTY_IS_NULL );
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
if ( bHasEmptyIsNULL )
OSL_VERIFY( impl_getPropertyValue_throw( PROPERTY_EMPTY_IS_NULL ) >>= bEmptyIsNULL );
// if the control is not bound to a DB field, there is no sense in having the "Input required"
// property
// Also, if an empty input of this control are *not* written as NULL, but as empty strings,
// then "Input required" does not make sense, too (since there's always an input, even if the control
// is empty).
_rxInspectorUI->enablePropertyUI( PROPERTY_INPUT_REQUIRED,
( !sControlSource.isEmpty() ) && ( !bHasEmptyIsNULL || bEmptyIsNULL )
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
);
}
break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
// ----- SelectedItems, DefaultSelection -----
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
case PROPERTY_ID_SELECTEDITEMS:
case PROPERTY_ID_DEFAULT_SELECT_SEQ:
{
Sequence< OUString > aEntries;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
impl_getPropertyValue_throw( PROPERTY_STRINGITEMLIST ) >>= aEntries;
bool isEnabled = aEntries.getLength() != 0;
if ( ( m_nClassId == FormComponentType::LISTBOX ) && ( m_eComponentClass == eFormControl ) )
{
ListSourceType eLSType = ListSourceType_VALUELIST;
impl_getPropertyValue_throw( PROPERTY_LISTSOURCETYPE ) >>= eLSType;
isEnabled &= ( eLSType == ListSourceType_VALUELIST );
}
_rxInspectorUI->enablePropertyUIElements( impl_getPropertyNameFromId_nothrow( _nPropId ),
PropertyLineElement::PrimaryButton, isEnabled );
}
break; // case PROPERTY_ID_DEFAULT_SELECT_SEQ
// ----- TargetFrame ------
case PROPERTY_ID_TARGET_FRAME:
{
OUString sTargetURL;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
impl_getPropertyValue_throw( PROPERTY_TARGET_URL ) >>= sTargetURL;
FormButtonType eButtonType( FormButtonType_URL );
if ( 0 != m_nClassId )
{
OSL_VERIFY( impl_getPropertyValue_throw( PROPERTY_BUTTONTYPE ) >>= eButtonType );
}
// if m_nClassId is 0, then we're inspecting a form. In this case, eButtonType is always
// FormButtonType_URL here
_rxInspectorUI->enablePropertyUI( PROPERTY_TARGET_FRAME,
( eButtonType == FormButtonType_URL ) && ( !sTargetURL.isEmpty() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
);
}
break;
// ----- Order ------
case PROPERTY_ID_SORT:
// ----- Filter ------
case PROPERTY_ID_FILTER:
{
Reference< XConnection > xConnection;
bool bAllowEmptyDS = ::dbtools::isEmbeddedInDatabase( m_xComponent, xConnection );
// if there's no escape processing, we cannot enter any values for this property
bool bDoEscapeProcessing( false );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
impl_getPropertyValue_throw( PROPERTY_ESCAPE_PROCESSING ) >>= bDoEscapeProcessing;
_rxInspectorUI->enablePropertyUI(
impl_getPropertyNameFromId_nothrow( _nPropId ),
bDoEscapeProcessing
);
// also care for the browse button - enabled if we have escape processing, and a valid
// data source signature
_rxInspectorUI->enablePropertyUIElements(
impl_getPropertyNameFromId_nothrow( _nPropId ),
PropertyLineElement::PrimaryButton,
impl_hasValidDataSourceSignature_nothrow( m_xComponent, bAllowEmptyDS )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
&& bDoEscapeProcessing
);
}
break; // case PROPERTY_ID_FILTER:
// ----- Command -----
case PROPERTY_ID_COMMAND:
{
sal_Int32 nCommandType( CommandType::COMMAND );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( impl_getPropertyValue_throw( PROPERTY_COMMANDTYPE ) >>= nCommandType );
impl_ensureRowsetConnection_nothrow();
Reference< XConnection > xConnection = m_xRowSetConnection.getTyped();
bool bAllowEmptyDS = false;
if ( !xConnection.is() )
bAllowEmptyDS = ::dbtools::isEmbeddedInDatabase( m_xComponent, xConnection );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool doEnable = ( nCommandType == CommandType::COMMAND )
&& ( m_xRowSetConnection.is()
|| xConnection.is()
|| impl_hasValidDataSourceSignature_nothrow( m_xComponent, bAllowEmptyDS)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
);
_rxInspectorUI->enablePropertyUIElements(
PROPERTY_COMMAND,
PropertyLineElement::PrimaryButton,
doEnable
);
}
break; // case PROPERTY_ID_COMMAND
// ----- DetailFields -----
case PROPERTY_ID_DETAILFIELDS:
{
Reference< XConnection > xConnection;
bool bAllowEmptyDS = ::dbtools::isEmbeddedInDatabase( m_xComponent, xConnection );
// both our current form, and its parent form, need to have a valid
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// data source signature
bool bDoEnableMasterDetailFields =
impl_hasValidDataSourceSignature_nothrow( m_xComponent, bAllowEmptyDS )
&& impl_hasValidDataSourceSignature_nothrow( Reference< XPropertySet >( m_xObjectParent, UNO_QUERY ), bAllowEmptyDS );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// in opposite to the other properties, here in real *two* properties are
// affected
_rxInspectorUI->enablePropertyUIElements( PROPERTY_DETAILFIELDS, PropertyLineElement::PrimaryButton, bDoEnableMasterDetailFields );
_rxInspectorUI->enablePropertyUIElements( PROPERTY_MASTERFIELDS, PropertyLineElement::PrimaryButton, bDoEnableMasterDetailFields );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
default:
OSL_FAIL( "FormComponentPropertyHandler::impl_updateDependentProperty_nothrow: unexpected property to update!" );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
} // switch
}
catch( const Exception& )
{
OSL_FAIL( "FormComponentPropertyHandler::impl_updateDependentProperty_nothrow: caught an exception!" );
DBG_UNHANDLED_EXCEPTION();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
void SAL_CALL FormComponentPropertyHandler::disposing()
{
FormComponentPropertyHandler_Base::disposing();
if ( m_xCommandDesigner.is() && m_xCommandDesigner->isActive() )
m_xCommandDesigner->dispose();
}
sal_Bool SAL_CALL FormComponentPropertyHandler::suspend( sal_Bool _bSuspend ) throw (RuntimeException, std::exception)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
::osl::MutexGuard aGuard( m_aMutex );
if ( _bSuspend )
if ( m_xCommandDesigner.is() && m_xCommandDesigner->isActive() )
return m_xCommandDesigner->suspend();
return sal_True;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
void FormComponentPropertyHandler::impl_initComponentMetaData_throw()
{
try
{
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// component class
m_eComponentClass = eUnknown;
if ( impl_componentHasProperty_throw( PROPERTY_WIDTH )
&& impl_componentHasProperty_throw( PROPERTY_HEIGHT )
&& impl_componentHasProperty_throw( PROPERTY_POSITIONX )
&& impl_componentHasProperty_throw( PROPERTY_POSITIONY )
&& impl_componentHasProperty_throw( PROPERTY_STEP )
&& impl_componentHasProperty_throw( PROPERTY_TABINDEX )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
)
{
m_eComponentClass = eDialogControl;
}
else
{
m_eComponentClass = eFormControl;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// (database) sub form?
Reference< XForm > xAsForm( m_xComponent, UNO_QUERY );
if ( xAsForm.is() )
{
Reference< XForm > xFormsParent( xAsForm->getParent(), css::uno::UNO_QUERY );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
m_bComponentIsSubForm = xFormsParent.is();
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// ClassId
Reference< XChild > xCompAsChild( m_xComponent, UNO_QUERY );
if ( xCompAsChild.is() )
m_xObjectParent = xCompAsChild->getParent();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// ClassId
impl_classifyControlModel_throw();
}
catch( const RuntimeException& )
{
throw;
}
catch( const Exception& )
{
OSL_FAIL( "FormComponentPropertyHandler::impl_initComponentMetaData_throw: caught an exception!" );
DBG_UNHANDLED_EXCEPTION();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
void FormComponentPropertyHandler::impl_classifyControlModel_throw( )
{
if ( impl_componentHasProperty_throw( PROPERTY_CLASSID ) )
{
OSL_VERIFY( m_xComponent->getPropertyValue( PROPERTY_CLASSID ) >>= m_nClassId );
}
else if ( eDialogControl == m_eComponentClass )
{
Reference< XControlModel > xControlModel( m_xComponent, UNO_QUERY );
Reference< XServiceInfo > xServiceInfo( m_xComponent, UNO_QUERY );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( xServiceInfo.is() )
{
// it's a control model, and can tell about it's supported services
m_nClassId = FormComponentType::CONTROL;
const sal_Char* aControlModelServiceNames[] =
{
"UnoControlButtonModel",
"UnoControlCheckBoxModel",
"UnoControlComboBoxModel",
"UnoControlCurrencyFieldModel",
"UnoControlDateFieldModel",
"UnoControlEditModel",
"UnoControlFileControlModel",
"UnoControlFixedTextModel",
"UnoControlGroupBoxModel",
"UnoControlImageControlModel",
"UnoControlListBoxModel",
"UnoControlNumericFieldModel",
"UnoControlPatternFieldModel",
"UnoControlRadioButtonModel",
"UnoControlScrollBarModel",
"UnoControlSpinButtonModel",
"UnoControlTimeFieldModel",
"UnoControlFixedLineModel",
"UnoControlFormattedFieldModel",
"UnoControlProgressBarModel"
};
const sal_Int16 nClassIDs[] =
{
FormComponentType::COMMANDBUTTON,
FormComponentType::CHECKBOX,
FormComponentType::COMBOBOX,
FormComponentType::CURRENCYFIELD,
FormComponentType::DATEFIELD,
FormComponentType::TEXTFIELD,
FormComponentType::FILECONTROL,
FormComponentType::FIXEDTEXT,
FormComponentType::GROUPBOX,
FormComponentType::IMAGECONTROL,
FormComponentType::LISTBOX,
FormComponentType::NUMERICFIELD,
FormComponentType::PATTERNFIELD,
FormComponentType::RADIOBUTTON,
FormComponentType::SCROLLBAR,
FormComponentType::SPINBUTTON,
FormComponentType::TIMEFIELD,
ControlType::FIXEDLINE,
ControlType::FORMATTEDFIELD,
ControlType::PROGRESSBAR
};
2010-10-15 18:15:35 +01:00
sal_Int32 nKnownControlTypes = SAL_N_ELEMENTS( aControlModelServiceNames );
OSL_ENSURE( nKnownControlTypes == SAL_N_ELEMENTS( nClassIDs ),
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
"FormComponentPropertyHandler::impl_classifyControlModel_throw: inconsistence" );
for ( sal_Int32 i = 0; i < nKnownControlTypes; ++i )
{
OUString sServiceName( "com.sun.star.awt." );
sServiceName += OUString::createFromAscii( aControlModelServiceNames[ i ] );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( xServiceInfo->supportsService( sServiceName ) )
{
m_nClassId = nClassIDs[ i ];
break;
}
}
}
}
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
void FormComponentPropertyHandler::impl_normalizePropertyValue_nothrow( Any& _rValue, PropertyId _nPropId ) const
{
switch ( _nPropId )
{
case PROPERTY_ID_TABSTOP:
if ( !_rValue.hasValue() )
{
switch ( m_nClassId )
{
case FormComponentType::COMMANDBUTTON:
case FormComponentType::RADIOBUTTON:
case FormComponentType::CHECKBOX:
case FormComponentType::TEXTFIELD:
case FormComponentType::LISTBOX:
case FormComponentType::COMBOBOX:
case FormComponentType::FILECONTROL:
case FormComponentType::DATEFIELD:
case FormComponentType::TIMEFIELD:
case FormComponentType::NUMERICFIELD:
case ControlType::FORMATTEDFIELD:
case FormComponentType::CURRENCYFIELD:
case FormComponentType::PATTERNFIELD:
_rValue = makeAny( true );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
default:
_rValue = makeAny( false );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
break;
}
}
break;
}
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool FormComponentPropertyHandler::impl_shouldExcludeProperty_nothrow( const Property& _rProperty ) const
{
OSL_ENSURE( _rProperty.Handle == m_pInfoService->getPropertyId( _rProperty.Name ),
"FormComponentPropertyHandler::impl_shouldExcludeProperty_nothrow: insonsistency in the property!" );
if ( _rProperty.Handle == PROPERTY_ID_CONTROLLABEL )
// prevent that this is caught below
return false;
if ( ( _rProperty.Type.getTypeClass() == TypeClass_INTERFACE )
|| ( _rProperty.Type.getTypeClass() == TypeClass_UNKNOWN )
)
return true;
if ( ( _rProperty.Attributes & PropertyAttribute::TRANSIENT ) && ( m_eComponentClass != eDialogControl ) )
// strange enough, dialog controls declare a lot of their properties as transient
return true;
if ( _rProperty.Attributes & PropertyAttribute::READONLY )
return true;
switch ( _rProperty.Handle )
{
case PROPERTY_ID_MASTERFIELDS:
case PROPERTY_ID_DETAILFIELDS:
if ( !m_bComponentIsSubForm )
// no master and detail fields for forms which are no sub forms
return true;
break;
case PROPERTY_ID_DATASOURCE:
{
// don't show DataSource if the component is part of an embedded form document
Reference< XConnection > xConn;
if ( isEmbeddedInDatabase( m_xComponent, xConn ) )
return true;
}
break;
case PROPERTY_ID_TEXT:
// don't show the "Text" property of formatted fields
if ( ControlType::FORMATTEDFIELD == m_nClassId )
return true;
break;
case PROPERTY_ID_FORMATKEY:
case PROPERTY_ID_EFFECTIVE_MIN:
case PROPERTY_ID_EFFECTIVE_MAX:
case PROPERTY_ID_EFFECTIVE_DEFAULT:
case PROPERTY_ID_EFFECTIVE_VALUE:
// only if the set has a formats supplier, too
if ( !impl_componentHasProperty_throw( PROPERTY_FORMATSSUPPLIER ) )
return true;
// (form) date and time fields also have a formats supplier, but the format itself
// is reflected in another property
if ( ( FormComponentType::DATEFIELD == m_nClassId )
|| ( FormComponentType::TIMEFIELD == m_nClassId )
)
return true;
break;
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
case PROPERTY_ID_SCALEIMAGE:
if ( impl_componentHasProperty_throw( PROPERTY_SCALE_MODE ) )
// ScaleImage is superseded by ScaleMode
return true;
break;
CWS-TOOLING: integrate CWS rtlcontrols 2008-12-11 21:08:49 +0100 fs r265367 : CONTEXT_WRITING_MODE is transient 2008-12-11 21:08:00 +0100 fs r265365 : REGISTER_PROP_3 2008-12-11 20:53:44 +0100 fs r265362 : ContextWritingMode is not MAYBEVOID 2008-12-11 15:29:08 +0100 fs r265315 : prevent a deadlock during complex.dbaccess.DatabaseDocument test 2008-12-11 15:01:13 +0100 fs r265304 : manual RESYNC to m37 2008-12-10 20:04:38 +0100 pl r265230 : #i30631# fix a snafu in mirroring 2008-12-10 19:14:45 +0100 pl r265229 : #i30631# rework PaintToDevice for RTL controls 2008-12-05 10:19:13 +0100 fs r264893 : #i10000# ImplInitSettings => ImplInitWindow (ImplInitSettings clashed with base classes ImplInitSettings on unxsols4) 2008-12-03 12:55:24 +0100 fs r264768 : #i100000# 2008-12-03 07:11:48 +0100 fs r264741 : #i10000# 2008-12-02 10:37:51 +0100 fs r264670 : CWS-TOOLING: rebase CWS rtlcontrols to trunk@264325 (milestone: DEV300:m36) 2008-12-02 09:27:50 +0100 fs r264660 : merge from trunk 2008-11-25 10:28:36 +0100 ama r264277 : Fix #i94572# 2008-11-24 11:46:48 +0100 fs r264218 : #i30631# proper context writing mode 2008-11-24 09:38:04 +0100 fs r264204 : #i30631# (approved by PL) 2008-11-24 09:35:47 +0100 fs r264203 : #i30631# Context/WritingMode 2008-11-24 09:33:36 +0100 fs r264202 : #i30631# Context/WritingMode 2008-11-24 09:31:53 +0100 fs r264200 : #i30631# RTL 2008-11-19 08:51:48 +0100 fs r263963 : #i10000# 2008-11-18 20:58:11 +0100 fs r263878 : #i10000# 2008-11-18 15:30:44 +0100 fs r263778 : migrate the CWS from CVS to SVN the CVS changes contained in this change set are the ones between the following two CVS tags: CWS_DEV300_RTLCONTROLS_ANCHOR CWS_DEV300_RTLCONTROLS_PRE_MIGRATION 2008-11-18 12:29:04 +0100 ama r263762 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:25:50 +0100 ama r263761 : Fix #i94572#: Context direction for drawing objects 2008-11-18 12:02:30 +0100 ama r263759 : Fix #i94572#: Context direction for drawing objects
2008-12-16 13:30:53 +00:00
case PROPERTY_ID_WRITING_MODE:
if ( !SvtCTLOptions().IsCTLFontEnabled() )
return true;
break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
sal_uInt32 nPropertyUIFlags = m_pInfoService->getPropertyUIFlags( _rProperty.Handle );
// don't show experimental properties unless allowed to do so
if ( ( nPropertyUIFlags & PROP_FLAG_EXPERIMENTAL ) != 0 )
{
if ( true ) // TODO
return true;
}
// no data properties if no Base is installed. #124939#
// This fix is not intendend to appear on the main trunk. If you find it there,
// please tell me! frank.schoenheit@sun.com
if ( ( nPropertyUIFlags & PROP_FLAG_DATA_PROPERTY ) != 0 )
if ( !SvtModuleOptions().IsModuleInstalled( SvtModuleOptions::EModule::DATABASE ) )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
return true;
return false;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Reference< XRowSet > FormComponentPropertyHandler::impl_getRowSet_throw( ) const
{
Reference< XRowSet > xRowSet = m_xRowSet;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( !xRowSet.is() )
{
xRowSet.set( m_xComponent, UNO_QUERY );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( !xRowSet.is() )
{
xRowSet.set( m_xObjectParent, UNO_QUERY );
if ( !xRowSet.is() )
{
// are we inspecting a grid column?
if (Reference< XGridColumnFactory >( m_xObjectParent, UNO_QUERY) .is())
{ // yes
Reference< XChild > xParentAsChild( m_xObjectParent, UNO_QUERY );
if ( xParentAsChild.is() )
xRowSet.set( xParentAsChild->getParent(), UNO_QUERY );
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
if ( !xRowSet.is() )
xRowSet = m_xRowSet;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
DBG_ASSERT( xRowSet.is(), "FormComponentPropertyHandler::impl_getRowSet_throw: could not obtain the rowset for the introspectee!" );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
return xRowSet;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Reference< XRowSet > FormComponentPropertyHandler::impl_getRowSet_nothrow( ) const
{
Reference< XRowSet > xReturn;
try
{
xReturn = impl_getRowSet_throw();
}
catch( const Exception& )
{
OSL_FAIL( "FormComponentPropertyHandler::impl_getRowSet_nothrow: caught an exception!" );
DBG_UNHANDLED_EXCEPTION();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
return xReturn;
}
void FormComponentPropertyHandler::impl_initFieldList_nothrow( ::std::vector< OUString >& _rFieldNames ) const
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
clearContainer( _rFieldNames );
try
{
WaitCursor aWaitCursor( impl_getDefaultDialogParent_nothrow() );
Reference< XPreparedStatement > xStatement;
// get the form of the control we're inspecting
Reference< XPropertySet > xFormSet( impl_getRowSet_throw(), UNO_QUERY );
if ( !xFormSet.is() )
return;
OUString sObjectName;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( xFormSet->getPropertyValue( PROPERTY_COMMAND ) >>= sObjectName );
// when there is no command we don't need to ask for columns
if ( !sObjectName.isEmpty() && impl_ensureRowsetConnection_nothrow() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
OUString aDatabaseName;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( xFormSet->getPropertyValue( PROPERTY_DATASOURCE ) >>= aDatabaseName );
sal_Int32 nObjectType = CommandType::COMMAND;
OSL_VERIFY( xFormSet->getPropertyValue( PROPERTY_COMMANDTYPE ) >>= nObjectType );
Sequence< OUString > aFields( ::dbtools::getFieldNamesByCommandDescriptor( m_xRowSetConnection, nObjectType, sObjectName ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
const OUString* pFields = aFields.getConstArray();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
for ( sal_Int32 i = 0; i < aFields.getLength(); ++i, ++pFields )
_rFieldNames.push_back( *pFields );
}
}
2011-12-10 22:14:57 +09:00
catch (const Exception&)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
2011-03-01 17:55:09 +01:00
OSL_FAIL( "FormComponentPropertyHandler::impl_initFieldList_nothrow: caught an exception!" );
DBG_UNHANDLED_EXCEPTION();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
void FormComponentPropertyHandler::impl_clearRowsetConnection_nothrow()
{
m_xRowSetConnection.clear();
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
void FormComponentPropertyHandler::impl_displaySQLError_nothrow( const ::dbtools::SQLExceptionInfo& _rErrorDescriptor ) const
{
::dbtools::showError( _rErrorDescriptor, VCLUnoHelper::GetInterface( impl_getDefaultDialogParent_nothrow() ), m_xContext );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool FormComponentPropertyHandler::impl_ensureRowsetConnection_nothrow() const
{
if ( !m_xRowSetConnection.is() )
{
uno::Reference<sdbc::XConnection> xConnection;
Any any = m_xContext->getValueByName( "ActiveConnection" );
any >>= xConnection;
m_xRowSetConnection.reset(xConnection,::dbtools::SharedConnection::NoTakeOwnership);
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( m_xRowSetConnection.is() )
return true;
Reference< XRowSet > xRowSet( impl_getRowSet_throw() );
Reference< XPropertySet > xRowSetProps( xRowSet, UNO_QUERY );
// connect the row set - this is delegated to elsewhere - while observing errors
SQLExceptionInfo aError;
try
{
if ( xRowSetProps.is() )
{
WaitCursor aWaitCursor( impl_getDefaultDialogParent_nothrow() );
m_xRowSetConnection = ::dbtools::ensureRowSetConnection( xRowSet, m_xContext, false );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
catch ( const SQLException& ) { aError = SQLExceptionInfo( ::cppu::getCaughtException() ); }
catch ( const WrappedTargetException& e ) { aError = SQLExceptionInfo( e.TargetException ); }
catch ( const Exception& ) { DBG_UNHANDLED_EXCEPTION(); }
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// report errors, if necessary
if ( aError.isValid() )
{
OUString sDataSourceName;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
try
{
xRowSetProps->getPropertyValue( PROPERTY_DATASOURCE ) >>= sDataSourceName;
}
catch( const Exception& )
{
2011-03-01 17:55:09 +01:00
OSL_FAIL( "FormComponentPropertyHandler::impl_ensureRowsetConnection_nothrow: caught an exception during error handling!" );
DBG_UNHANDLED_EXCEPTION();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
Many spelling fixes: directories a* - g*. Attempt to clean up most but certainly not all the spelling mistakes that found home in OpenOffice through decades. We could probably blame the international nature of the code but it is somewhat shameful that this wasn't done before. (cherry picked from commit a6efc99d19d533fcf53106b6667bafba4d364370) Conflicts: accessibility/bridge/org/openoffice/java/accessibility/AccessibleTextImpl.java accessibility/bridge/org/openoffice/java/accessibility/Component.java accessibility/bridge/org/openoffice/java/accessibility/Container.java accessibility/bridge/org/openoffice/java/accessibility/DescendantManager.java accessibility/bridge/org/openoffice/java/accessibility/Dialog.java accessibility/bridge/org/openoffice/java/accessibility/Frame.java accessibility/bridge/org/openoffice/java/accessibility/List.java accessibility/bridge/org/openoffice/java/accessibility/Menu.java accessibility/bridge/org/openoffice/java/accessibility/Table.java accessibility/bridge/org/openoffice/java/accessibility/Tree.java accessibility/bridge/org/openoffice/java/accessibility/Window.java accessibility/bridge/source/java/WindowsAccessBridgeAdapter.cxx accessibility/inc/accessibility/extended/AccessibleBrowseBoxBase.hxx accessibility/inc/accessibility/extended/AccessibleGridControlBase.hxx accessibility/inc/accessibility/standard/vclxaccessiblebox.hxx accessibility/source/extended/accessibleiconchoicectrlentry.cxx accessibility/source/extended/accessiblelistboxentry.cxx accessibility/source/extended/accessibletablistbox.cxx accessibility/source/extended/accessibletablistboxtable.cxx accessibility/workben/org/openoffice/accessibility/awb/canvas/Canvas.java accessibility/workben/org/openoffice/accessibility/misc/OfficeConnection.java apple_remote/AppleRemote.m autodoc/inc/ary/cpp/c_gate.hxx autodoc/inc/ary/cpp/cp_ce.hxx autodoc/inc/ary/cpp/cp_def.hxx autodoc/inc/ary/cpp/cp_type.hxx autodoc/inc/ary/doc/d_parametrized.hxx autodoc/inc/ary/idl/i_type.hxx autodoc/source/ary/inc/cross_refs.hxx autodoc/source/ary/inc/sorted_idset.hxx autodoc/source/display/html/outfile.hxx autodoc/source/display/html/pagemake.cxx autodoc/source/display/idl/hi_env.hxx autodoc/source/parser/inc/tokens/tokproct.hxx autodoc/source/parser_i/inc/s2_luidl/tokproct.hxx autodoc/source/parser_i/inc/tokens/tkp2.hxx automation/inc/automation/commtypes.hxx automation/inc/automation/simplecm.hxx automation/source/server/recorder.cxx automation/source/server/recorder.hxx automation/source/server/statemnt.cxx automation/source/simplecm/packethandler.hxx automation/source/simplecm/simplecm.cxx avmedia/source/framework/soundhandler.cxx basegfx/inc/basegfx/range/rangeexpander.hxx basic/inc/basic/sbxdef.hxx basic/source/classes/sbunoobj.cxx basic/source/classes/sbxmod.cxx basic/source/comp/dim.cxx basic/source/comp/exprgen.cxx basic/source/runtime/step1.cxx basic/source/runtime/step2.cxx basic/source/sbx/sbxint.cxx basic/source/uno/namecont.cxx basic/workben/mgrtest.cxx bean/com/sun/star/beans/LocalOfficeConnection.java bean/com/sun/star/beans/LocalOfficeWindow.java bean/com/sun/star/comp/beans/LocalOfficeConnection.java bean/com/sun/star/comp/beans/LocalOfficeWindow.java bean/com/sun/star/comp/beans/OOoBean.java bridges/inc/bridges/cpp_uno/bridge.hxx bridges/source/cpp_uno/cc50_solaris_intel/cpp2uno.cxx bridges/source/cpp_uno/cc50_solaris_intel/except.cxx bridges/source/cpp_uno/cc50_solaris_intel/uno2cpp.cxx bridges/source/cpp_uno/cc50_solaris_sparc/cpp2uno.cxx bridges/source/cpp_uno/cc50_solaris_sparc/except.cxx bridges/source/cpp_uno/cc50_solaris_sparc/uno2cpp.cxx bridges/source/cpp_uno/gcc3_linux_x86-64/uno2cpp.cxx bridges/source/cpp_uno/gcc3_macosx_powerpc/cpp2uno.cxx bridges/source/cpp_uno/gcc3_macosx_x86-64/uno2cpp.cxx bridges/source/cpp_uno/gcc3_netbsd_intel/cpp2uno.cxx bridges/source/cpp_uno/gcc3_netbsd_intel/except.cxx bridges/source/cpp_uno/gcc3_netbsd_intel/uno2cpp.cxx bridges/source/cpp_uno/gcc3_os2_intel/cpp2uno.cxx bridges/source/cpp_uno/gcc3_os2_intel/except.cxx bridges/source/cpp_uno/gcc3_os2_intel/uno2cpp.cxx bridges/source/cpp_uno/mingw_x86-64/uno2cpp.cxx bridges/source/cpp_uno/msvc_win32_intel/except.cxx bridges/source/cpp_uno/s5abi_macosx_x86-64/except.cxx bridges/source/cpp_uno/shared/component.cxx bridges/source/jni_uno/jni_base.h bridges/source/jni_uno/jni_bridge.cxx bridges/source/jni_uno/jni_java2uno.cxx bridges/source/jni_uno/jni_uno2java.cxx canvas/inc/canvas/base/doublebitmapbase.hxx canvas/inc/canvas/base/floatbitmapbase.hxx canvas/inc/canvas/base/integerbitmapbase.hxx canvas/source/cairo/cairo_canvasbitmap.cxx canvas/source/cairo/cairo_textlayout.cxx chart2/source/controller/dialogs/ObjectNameProvider.cxx chart2/source/view/diagram/VDiagram.cxx chart2/source/view/main/ChartView.cxx cli_ure/source/native/makefile.mk cli_ure/source/uno_bridge/cli_data.cxx codemaker/source/javamaker/javatype.cxx comphelper/inc/comphelper/componentcontext.hxx comphelper/inc/comphelper/interaction.hxx comphelper/inc/comphelper/locale.hxx comphelper/inc/comphelper/string.hxx comphelper/source/container/embeddedobjectcontainer.cxx comphelper/source/misc/accessiblecontexthelper.cxx comphelper/source/misc/asyncnotification.cxx comphelper/source/misc/locale.cxx comphelper/source/misc/mediadescriptor.cxx comphelper/source/misc/numberedcollection.cxx comphelper/source/misc/proxyaggregation.cxx comphelper/source/misc/scopeguard.cxx comphelper/source/misc/sequenceashashmap.cxx configure.in connectivity/source/commontools/parameters.cxx connectivity/source/drivers/dbase/DTable.cxx connectivity/source/drivers/evoab2/NStatement.cxx connectivity/source/drivers/file/FPreparedStatement.cxx connectivity/source/drivers/jdbc/DatabaseMetaData.cxx connectivity/source/inc/flat/ETable.hxx connectivity/source/parse/sqlnode.cxx cosv/inc/cosv/persist.hxx cosv/inc/cosv/ploc_dir.hxx cosv/inc/cosv/tpl/dyn.hxx cppu/source/LogBridge/LogBridge.cxx cppu/source/uno/data.cxx cppuhelper/source/bootstrap.cxx cppuhelper/source/component_context.cxx cppuhelper/source/propshlp.cxx cppuhelper/source/servicefactory.cxx cpputools/source/registercomponent/registercomponent.cxx cui/source/customize/acccfg.cxx cui/source/dialogs/about.cxx cui/source/dialogs/commonlingui.hxx cui/source/dialogs/showcols.cxx cui/source/inc/cuihyperdlg.hxx cui/source/inc/cuitabline.hxx cui/source/options/optsave.src cui/source/tabpages/tpline.cxx cui/source/tabpages/transfrm.cxx dbaccess/source/core/api/CacheSet.cxx dbaccess/source/core/api/KeySet.cxx dbaccess/source/core/api/RowSet.cxx dbaccess/source/core/api/RowSet.hxx dbaccess/source/core/api/RowSetBase.cxx dbaccess/source/core/api/RowSetBase.hxx dbaccess/source/core/api/RowSetCache.cxx dbaccess/source/core/api/querycomposer.cxx dbaccess/source/ext/adabas/Acomponentmodule.hxx dbaccess/source/ui/app/AppControllerDnD.cxx dbaccess/source/ui/app/AppDetailView.cxx dbaccess/source/ui/browser/brwctrlr.cxx dbaccess/source/ui/browser/sbagrid.cxx dbaccess/source/ui/browser/unodatbr.cxx dbaccess/source/ui/dlg/AdabasStat.hxx dbaccess/source/ui/dlg/UserAdmin.cxx dbaccess/source/ui/dlg/directsql.cxx dbaccess/source/ui/dlg/generalpage.hxx dbaccess/source/ui/dlg/tablespage.cxx dbaccess/source/ui/inc/JoinTableView.hxx dbaccess/source/ui/inc/TableController.hxx dbaccess/source/ui/inc/UITools.hxx dbaccess/source/ui/inc/brwctrlr.hxx dbaccess/source/ui/inc/datasourcemap.hxx dbaccess/source/ui/querydesign/JoinTableView.cxx dbaccess/source/ui/querydesign/QueryDesignView.cxx dbaccess/source/ui/querydesign/SelectionBrowseBox.cxx dbaccess/source/ui/querydesign/TableWindow.cxx dbaccess/source/ui/querydesign/querycontroller.cxx dbaccess/source/ui/relationdesign/RelationTableView.cxx dbaccess/source/ui/tabledesign/TableController.cxx desktop/source/app/app.cxx desktop/source/app/appinit.cxx desktop/source/app/langselect.cxx desktop/source/app/officeipcthread.cxx desktop/source/deployment/manager/dp_extensionmanager.cxx desktop/source/deployment/misc/dp_misc.cxx desktop/source/deployment/misc/dp_resource.cxx desktop/source/deployment/registry/dp_backend.cxx desktop/source/deployment/registry/package/dp_package.cxx desktop/source/migration/cfgfilter.cxx desktop/source/migration/migration.cxx desktop/source/splash/splash.cxx desktop/win32/source/QuickStart/QuickStart.cpp desktop/win32/source/setup/setup.cpp drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx dtrans/source/win32/clipb/MtaOleClipb.hxx dtrans/source/win32/clipb/WinClipbImpl.cxx editeng/source/editeng/editview.cxx editeng/source/editeng/impedit2.cxx editeng/source/editeng/impedit3.cxx editeng/source/editeng/impedit4.cxx editeng/source/editeng/textconv.hxx editeng/source/misc/unolingu.cxx embeddedobj/source/commonembedding/persistence.cxx embeddedobj/source/general/dummyobject.cxx embeddedobj/source/msole/olecomponent.cxx embeddedobj/source/msole/olepersist.cxx embeddedobj/test/Container1/NativeView.java extensions/source/bibliography/framectr.cxx extensions/source/macosx/spotlight/OOoContentDataParser.m extensions/source/macosx/spotlight/unzip.h extensions/source/macosx/spotlight/unzip.m extensions/source/oooimprovement/myconfigurationhelper.hxx extensions/source/propctrlr/eventhandler.cxx extensions/source/propctrlr/formcomponenthandler.cxx extensions/source/propctrlr/pcrcomponentcontext.hxx extensions/source/scanner/twain.cxx extensions/source/update/check/updatecheckconfig.hxx external/mingwheaders/mingw_atl_headers.patch extras/source/misc_config/wizard/web/layouts/source.xml.xsl fileaccess/source/FileAccess.cxx filter/inc/filter/msfilter/msocximex.hxx filter/inc/filter/msfilter/svxmsbas.hxx filter/qa/complex/filter/detection/typeDetection/Helper.java filter/source/config/cache/basecontainer.cxx filter/source/config/cache/cacheitem.hxx filter/source/config/cache/contenthandlerfactory.cxx filter/source/config/cache/filtercache.cxx filter/source/config/cache/filtercache.hxx filter/source/config/cache/filterfactory.cxx filter/source/config/cache/frameloaderfactory.cxx filter/source/config/cache/querytokenizer.hxx filter/source/config/cache/typedetection.cxx filter/source/config/cache/typedetection.hxx filter/source/config/cache/versions.hxx filter/source/config/fragments/makefile.mk filter/source/config/tools/merge/pyAltFCFGMerge filter/source/flash/swfwriter.cxx filter/source/flash/swfwriter1.cxx filter/source/msfilter/msdffimp.cxx filter/source/msfilter/msocximex.cxx filter/source/msfilter/msvbahelper.cxx filter/source/msfilter/svxmsbas.cxx filter/source/xmlfilterdetect/filterdetect.cxx filter/source/xslt/import/uof2/uof2odf.xsl filter/source/xslt/odf2xhtml/export/xhtml/body.xsl filter/source/xsltfilter/com/sun/star/comp/xsltfilter/Base64.java forms/source/xforms/convert.hxx forms/source/xforms/model.cxx fpicker/source/aqua/SalAquaFilePicker.mm fpicker/source/office/fpinteraction.cxx fpicker/source/unx/gnome/SalGtkFolderPicker.cxx fpicker/source/unx/kde4/KDE4FilePicker.cxx fpicker/source/win32/filepicker/PreviewCtrl.cxx fpicker/source/win32/filepicker/PreviewCtrl.hxx fpicker/source/win32/filepicker/VistaFilePicker.cxx fpicker/source/win32/filepicker/VistaFilePickerImpl.hxx fpicker/source/win32/filepicker/helppopupwindow.hxx fpicker/source/win32/folderpicker/MtaFop.hxx framework/inc/classes/droptargetlistener.hxx framework/inc/classes/filtercache.hxx framework/inc/classes/filtercachedata.hxx framework/inc/classes/protocolhandlercache.hxx framework/inc/classes/servicemanager.hxx framework/inc/commands.h framework/inc/dispatch/basedispatcher.hxx framework/inc/dispatch/blankdispatcher.hxx framework/inc/dispatch/closedispatcher.hxx framework/inc/dispatch/createdispatcher.hxx framework/inc/dispatch/dispatchprovider.hxx framework/inc/dispatch/helpagentdispatcher.hxx framework/inc/dispatch/mailtodispatcher.hxx framework/inc/dispatch/menudispatcher.hxx framework/inc/dispatch/oxt_handler.hxx framework/inc/dispatch/popupmenudispatcher.hxx framework/inc/dispatch/selfdispatcher.hxx framework/inc/dispatch/servicehandler.hxx framework/inc/dispatch/startmoduledispatcher.hxx framework/inc/dispatch/systemexec.hxx framework/inc/helper/fixeddocumentproperties.hxx framework/inc/helper/ocomponentaccess.hxx framework/inc/helper/oframes.hxx framework/inc/helper/otasksenumeration.hxx framework/inc/helper/persistentwindowstate.hxx framework/inc/helper/statusindicator.hxx framework/inc/helper/statusindicatorfactory.hxx framework/inc/helper/tagwindowasmodified.hxx framework/inc/helper/titlebarupdate.hxx framework/inc/helper/vclstatusindicator.hxx framework/inc/interaction/quietinteraction.hxx framework/inc/jobs/helponstartup.hxx framework/inc/jobs/job.hxx framework/inc/jobs/jobdata.hxx framework/inc/jobs/jobexecutor.hxx framework/inc/loadstate.h framework/inc/macros/debug/assertion.hxx framework/inc/macros/debug/event.hxx framework/inc/macros/debug/filterdbg.hxx framework/inc/macros/debug/memorymeasure.hxx framework/inc/macros/debug/timemeasure.hxx framework/inc/macros/xserviceinfo.hxx framework/inc/queries.h framework/inc/recording/dispatchrecordersupplier.hxx framework/inc/services/autorecovery.hxx framework/inc/services/backingcomp.hxx framework/inc/services/contenthandlerfactory.hxx framework/inc/services/desktop.hxx framework/inc/services/detectorfactory.hxx framework/inc/services/frame.hxx framework/inc/services/frameloaderfactory.hxx framework/inc/services/layoutmanager.hxx framework/inc/services/license.hxx framework/inc/services/logindialog.hxx framework/inc/services/modulemanager.hxx framework/inc/services/pathsettings.hxx framework/inc/services/pluginframe.hxx framework/inc/services/substitutepathvars.hxx framework/inc/services/task.hxx framework/inc/services/taskcreatorsrv.hxx framework/inc/stdtypes.h framework/inc/threadhelp/fairrwlock.hxx framework/inc/threadhelp/inoncopyable.h framework/inc/threadhelp/itransactionmanager.h framework/inc/threadhelp/lockhelper.hxx framework/inc/threadhelp/readguard.hxx framework/inc/threadhelp/resetableguard.hxx framework/inc/threadhelp/transactionguard.hxx framework/inc/threadhelp/writeguard.hxx framework/inc/uifactory/uielementfactorymanager.hxx framework/inc/xml/acceleratorconfigurationreader.hxx framework/qa/complex/dispatches/checkdispatchapi.java framework/qa/complex/framework/autosave/AutoSave.java framework/qa/complex/framework/autosave/Protocol.java framework/qa/complex/framework/recovery/RecoveryTest.java framework/qa/complex/loadAllDocuments/StreamSimulator.java framework/source/accelerators/acceleratorconfiguration.cxx framework/source/accelerators/acceleratorexecute.cxx framework/source/accelerators/acceleratorexecute.hxx framework/source/accelerators/keymapping.cxx framework/source/accelerators/presethandler.cxx framework/source/application/framework.cxx framework/source/application/login.cxx framework/source/classes/framecontainer.cxx framework/source/classes/menumanager.cxx framework/source/classes/taskcreator.cxx framework/source/dispatch/closedispatcher.cxx framework/source/dispatch/dispatchprovider.cxx framework/source/dispatch/helpagentdispatcher.cxx framework/source/dispatch/interceptionhelper.cxx framework/source/dispatch/mailtodispatcher.cxx framework/source/dispatch/menudispatcher.cxx framework/source/dispatch/oxt_handler.cxx framework/source/dispatch/servicehandler.cxx framework/source/fwe/classes/framelistanalyzer.cxx framework/source/fwe/dispatch/interaction.cxx framework/source/fwe/helper/titlehelper.cxx framework/source/fwe/helper/undomanagerhelper.cxx framework/source/fwe/xml/eventsdocumenthandler.cxx framework/source/fwe/xml/statusbardocumenthandler.cxx framework/source/fwe/xml/toolboxdocumenthandler.cxx framework/source/fwi/classes/protocolhandlercache.cxx framework/source/fwi/threadhelp/lockhelper.cxx framework/source/fwi/threadhelp/transactionmanager.cxx framework/source/helper/persistentwindowstate.cxx framework/source/helper/statusindicatorfactory.cxx framework/source/helper/vclstatusindicator.cxx framework/source/inc/accelerators/acceleratorcache.hxx framework/source/inc/accelerators/acceleratorconfiguration.hxx framework/source/inc/accelerators/presethandler.hxx framework/source/inc/accelerators/storageholder.hxx framework/source/inc/loadenv/actionlockguard.hxx framework/source/inc/loadenv/loadenv.hxx framework/source/inc/loadenv/loadenvexception.hxx framework/source/inc/pattern/frame.hxx framework/source/inc/pattern/storages.hxx framework/source/inc/pattern/window.hxx framework/source/jobs/helponstartup.cxx framework/source/jobs/job.cxx framework/source/jobs/jobdata.cxx framework/source/jobs/jobdispatch.cxx framework/source/jobs/jobresult.cxx framework/source/jobs/joburl.cxx framework/source/jobs/shelljob.cxx framework/source/loadenv/loadenv.cxx framework/source/services/autorecovery.cxx framework/source/services/backingwindow.cxx framework/source/services/desktop.cxx framework/source/services/frame.cxx framework/source/services/modulemanager.cxx framework/source/services/pathsettings.cxx framework/source/services/substitutepathvars.cxx framework/source/uiconfiguration/moduleuicfgsupplier.cxx framework/source/uiconfiguration/moduleuiconfigurationmanager.cxx framework/source/uiconfiguration/uicategorydescription.cxx framework/source/uiconfiguration/uiconfigurationmanagerimpl.cxx framework/source/uiconfiguration/windowstateconfiguration.cxx framework/source/uielement/uicommanddescription.cxx framework/source/unotypes/fwk.xml framework/source/xml/imagesdocumenthandler.cxx framework/test/test.cxx framework/test/test_componentenumeration.bas framework/test/test_statusindicatorfactory.bas framework/test/threadtest.cxx framework/test/threadtest/threadtest.cxx framework/test/typecfg/cfgview.cxx framework/test/typecfg/xml2xcd.cxx include/basegfx/polygon/b2dpolygon.hxx include/canvas/base/graphicdevicebase.hxx include/canvas/canvastools.hxx include/comphelper/configurationhelper.hxx include/comphelper/embeddedobjectcontainer.hxx include/comphelper/propagg.hxx include/comphelper/sequenceashashmap.hxx include/connectivity/sqlerror.hxx include/connectivity/sqlnode.hxx include/cppuhelper/propshlp.hxx include/editeng/AccessibleContextBase.hxx include/framework/framelistanalyzer.hxx sfx2/source/dialog/backingcomp.cxx vcl/unx/gtk/fpicker/SalGtkFilePicker.cxx Change-Id: I2618bf83c0e30f68f23ff25f6eb466df04d34c6d
2014-04-29 19:05:05 +00:00
// additional info about what happened
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
INetURLObject aParser( sDataSourceName );
if ( aParser.GetProtocol() != INetProtocol::NotValid )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
sDataSourceName = aParser.getBase( INetURLObject::LAST_SEGMENT, true, INetURLObject::DECODE_WITH_CHARSET );
OUString sInfo(PcrRes(RID_STR_UNABLETOCONNECT).toString().replaceAll("$name$", sDataSourceName));
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
SQLContext aContext;
aContext.Message = sInfo;
aContext.NextException = aError.get();
impl_displaySQLError_nothrow( aContext );
}
return m_xRowSetConnection.is();
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
void FormComponentPropertyHandler::impl_describeCursorSource_nothrow( LineDescriptor& _out_rProperty, const Reference< XPropertyControlFactory >& _rxControlFactory ) const
{
try
{
WaitCursor aWaitCursor( impl_getDefaultDialogParent_nothrow() );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// Setzen der UI-Daten
_out_rProperty.DisplayName = m_pInfoService->getPropertyTranslation( PROPERTY_ID_COMMAND );
_out_rProperty.HelpURL = HelpIdUrl::getHelpURL( m_pInfoService->getPropertyHelpId( PROPERTY_ID_COMMAND ) );
_out_rProperty.PrimaryButtonId = UID_PROP_DLG_SQLCOMMAND;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
sal_Int32 nCommandType = CommandType::COMMAND;
impl_getPropertyValue_throw( PROPERTY_COMMANDTYPE ) >>= nCommandType;
switch ( nCommandType )
{
case CommandType::TABLE:
case CommandType::QUERY:
{
::std::vector< OUString > aNames;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( impl_ensureRowsetConnection_nothrow() )
{
if ( nCommandType == CommandType::TABLE )
impl_fillTableNames_throw( aNames );
else
impl_fillQueryNames_throw( aNames );
}
_out_rProperty.Control = PropertyHandlerHelper::createComboBoxControl( _rxControlFactory, aNames, false, true );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
default:
_out_rProperty.Control = _rxControlFactory->createPropertyControl( PropertyControlType::MultiLineTextField, sal_False );
break;
}
}
2011-12-10 22:14:57 +09:00
catch (const Exception&)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
2011-03-01 17:55:09 +01:00
OSL_FAIL("FormComponentPropertyHandler::impl_describeCursorSource_nothrow: caught an exception !");
DBG_UNHANDLED_EXCEPTION();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
void FormComponentPropertyHandler::impl_fillTableNames_throw( ::std::vector< OUString >& _out_rNames ) const
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
OSL_PRECOND( m_xRowSetConnection.is(), "FormComponentPropertyHandler::impl_fillTableNames_throw: need a connection!" );
_out_rNames.resize( 0 );
Reference< XTablesSupplier > xSupplyTables( m_xRowSetConnection, UNO_QUERY );
Reference< XNameAccess > xTableNames;
if ( xSupplyTables.is() )
xTableNames = xSupplyTables->getTables();
DBG_ASSERT( xTableNames.is(), "FormComponentPropertyHandler::impl_fillTableNames_throw: no way to obtain the tables of the connection!" );
if ( !xTableNames.is() )
return;
Sequence< OUString> aTableNames = xTableNames->getElementNames();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
sal_uInt32 nCount = aTableNames.getLength();
const OUString* pTableNames = aTableNames.getConstArray();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
for ( sal_uInt32 i=0; i<nCount; ++i ,++pTableNames )
_out_rNames.push_back( *pTableNames );
}
void FormComponentPropertyHandler::impl_fillQueryNames_throw( ::std::vector< OUString >& _out_rNames ) const
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
OSL_PRECOND( m_xRowSetConnection.is(), "FormComponentPropertyHandler::impl_fillQueryNames_throw: need a connection!" );
_out_rNames.resize( 0 );
Reference< XQueriesSupplier > xSupplyQueries( m_xRowSetConnection, UNO_QUERY );
Reference< XNameAccess > xQueryNames;
if ( xSupplyQueries.is() )
2010-01-07 09:15:49 +01:00
{
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
xQueryNames = xSupplyQueries->getQueries();
2010-01-07 09:15:49 +01:00
impl_fillQueryNames_throw(xQueryNames,_out_rNames);
}
}
void FormComponentPropertyHandler::impl_fillQueryNames_throw( const Reference< XNameAccess >& _xQueryNames,::std::vector< OUString >& _out_rNames,const OUString& _sName ) const
2010-01-07 09:15:49 +01:00
{
DBG_ASSERT( _xQueryNames.is(), "FormComponentPropertyHandler::impl_fillQueryNames_throw: no way to obtain the queries of the connection!" );
if ( !_xQueryNames.is() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
return;
Sequence< OUString> aQueryNames = _xQueryNames->getElementNames();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
sal_uInt32 nCount = aQueryNames.getLength();
const OUString* pQueryNames = aQueryNames.getConstArray();
bool bAdd = !_sName.isEmpty();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
for ( sal_uInt32 i=0; i<nCount; i++, ++pQueryNames )
2010-01-07 09:15:49 +01:00
{
OUStringBuffer sTemp;
2010-01-07 09:15:49 +01:00
if ( bAdd )
{
sTemp.append(_sName);
sTemp.append("/");
2010-01-07 09:15:49 +01:00
}
sTemp.append(*pQueryNames);
Reference< XNameAccess > xSubQueries(_xQueryNames->getByName(*pQueryNames),UNO_QUERY);
if ( xSubQueries.is() )
impl_fillQueryNames_throw(xSubQueries,_out_rNames,sTemp.makeStringAndClear());
else
_out_rNames.push_back( sTemp.makeStringAndClear() );
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
void FormComponentPropertyHandler::impl_describeListSourceUI_throw( LineDescriptor& _out_rDescriptor, const Reference< XPropertyControlFactory >& _rxControlFactory ) const
{
OSL_PRECOND( m_xComponent.is(), "FormComponentPropertyHandler::impl_describeListSourceUI_throw: no component!" );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// Auslesen des ListSourceTypes
Any aListSourceType( m_xComponent->getPropertyValue( PROPERTY_LISTSOURCETYPE ) );
sal_Int32 nListSourceType = ListSourceType_VALUELIST;
::cppu::enum2int( nListSourceType, aListSourceType );
_out_rDescriptor.DisplayName = m_pInfoService->getPropertyTranslation( PROPERTY_ID_LISTSOURCE );
_out_rDescriptor.HelpURL = HelpIdUrl::getHelpURL( m_pInfoService->getPropertyHelpId( PROPERTY_ID_LISTSOURCE ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// Enums setzen
switch( nListSourceType )
{
case ListSourceType_VALUELIST:
_out_rDescriptor.Control = _rxControlFactory->createPropertyControl( PropertyControlType::StringListField, sal_False );
break;
case ListSourceType_TABLEFIELDS:
case ListSourceType_TABLE:
case ListSourceType_QUERY:
{
::std::vector< OUString > aListEntries;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( impl_ensureRowsetConnection_nothrow() )
{
if ( nListSourceType == ListSourceType_QUERY )
impl_fillQueryNames_throw( aListEntries );
else
impl_fillTableNames_throw( aListEntries );
}
_out_rDescriptor.Control = PropertyHandlerHelper::createComboBoxControl( _rxControlFactory, aListEntries, false, false );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
break;
case ListSourceType_SQL:
case ListSourceType_SQLPASSTHROUGH:
impl_ensureRowsetConnection_nothrow();
_out_rDescriptor.HasPrimaryButton = m_xRowSetConnection.is();
break;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
bool FormComponentPropertyHandler::impl_dialogListSelection_nothrow( const OUString& _rProperty, ::osl::ClearableMutexGuard& _rClearBeforeDialog ) const
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
OSL_PRECOND( m_pInfoService.get(), "FormComponentPropertyHandler::impl_dialogListSelection_nothrow: no property meta data!" );
OUString sPropertyUIName( m_pInfoService->getPropertyTranslation( m_pInfoService->getPropertyId( _rProperty ) ) );
ScopedVclPtrInstance< ListSelectionDialog > aDialog( impl_getDefaultDialogParent_nothrow(), m_xComponent, _rProperty, sPropertyUIName );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
_rClearBeforeDialog.clear();
return ( RET_OK == aDialog->Execute() );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
bool FormComponentPropertyHandler::impl_dialogFilterOrSort_nothrow( bool _bFilter, OUString& _out_rSelectedClause, ::osl::ClearableMutexGuard& _rClearBeforeDialog ) const
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
OSL_PRECOND( Reference< XRowSet >( m_xComponent, UNO_QUERY ).is(),
"FormComponentPropertyHandler::impl_dialogFilterOrSort_nothrow: to be called for forms only!" );
_out_rSelectedClause.clear();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool bSuccess = false;
SQLExceptionInfo aErrorInfo;
try
{
if ( !impl_ensureRowsetConnection_nothrow() )
return false;
// get a composer for the statement which the form is currently based on
Reference< XSingleSelectQueryComposer > xComposer( ::dbtools::getCurrentSettingsComposer( m_xComponent, m_xContext ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_ENSURE( xComposer.is(), "FormComponentPropertyHandler::impl_dialogFilterOrSort_nothrow: could not obtain a composer!" );
if ( !xComposer.is() )
return false;
OUString sPropertyUIName( m_pInfoService->getPropertyTranslation( _bFilter ? PROPERTY_ID_FILTER : PROPERTY_ID_SORT ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// create the dialog
Reference< XExecutableDialog > xDialog;
if ( _bFilter)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
xDialog.set( sdb::FilterDialog::createDefault(m_xContext) );
}
else
{
xDialog.set( sdb::OrderDialog::createDefault(m_xContext) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// initialize the dialog
Reference< XPropertySet > xDialogProps( xDialog, UNO_QUERY_THROW );
xDialogProps->setPropertyValue("QueryComposer", makeAny( xComposer ) );
xDialogProps->setPropertyValue("RowSet", makeAny( m_xComponent ) );
xDialogProps->setPropertyValue("ParentWindow", makeAny( VCLUnoHelper::GetInterface( impl_getDefaultDialogParent_nothrow() ) ) );
xDialogProps->setPropertyValue("Title", makeAny( sPropertyUIName ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
_rClearBeforeDialog.clear();
bSuccess = ( xDialog->execute() != 0 );
if ( bSuccess )
_out_rSelectedClause = _bFilter ? xComposer->getFilter() : xComposer->getOrder();
}
2011-12-10 22:14:57 +09:00
catch (const SQLContext& e) { aErrorInfo = e; }
catch (const SQLWarning& e) { aErrorInfo = e; }
catch (const SQLException& e) { aErrorInfo = e; }
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
catch( const Exception& )
{
OSL_FAIL( "FormComponentPropertyHandler::impl_dialogFilterOrSort_nothrow: caught an exception!" );
DBG_UNHANDLED_EXCEPTION();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
if ( aErrorInfo.isValid() )
impl_displaySQLError_nothrow( aErrorInfo );
return bSuccess;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool FormComponentPropertyHandler::impl_dialogLinkedFormFields_nothrow( ::osl::ClearableMutexGuard& _rClearBeforeDialog ) const
{
Reference< XForm > xDetailForm( m_xComponent, UNO_QUERY );
Reference< XForm > xMasterForm( m_xObjectParent, UNO_QUERY );
uno::Reference<beans::XPropertySet> xMasterProp(m_xObjectParent,uno::UNO_QUERY);
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_PRECOND( xDetailForm.is() && xMasterForm.is(), "FormComponentPropertyHandler::impl_dialogLinkedFormFields_nothrow: no forms!" );
if ( !xDetailForm.is() || !xMasterForm.is() )
return false;
ScopedVclPtrInstance< FormLinkDialog > aDialog( impl_getDefaultDialogParent_nothrow(), m_xComponent, xMasterProp, m_xContext );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
_rClearBeforeDialog.clear();
return ( RET_OK == aDialog->Execute() );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool FormComponentPropertyHandler::impl_dialogFormatting_nothrow( Any& _out_rNewValue, ::osl::ClearableMutexGuard& _rClearBeforeDialog ) const
{
bool bChanged = false;
try
{
// create the itemset for the dialog
SfxItemSet aCoreSet(SfxGetpApp()->GetPool(),
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
SID_ATTR_NUMBERFORMAT_VALUE, SID_ATTR_NUMBERFORMAT_VALUE,
SID_ATTR_NUMBERFORMAT_INFO, SID_ATTR_NUMBERFORMAT_INFO,
0); // ripped this somewhere ... don't understand it :(
// get the number formats supplier
Reference< XNumberFormatsSupplier > xSupplier;
m_xComponent->getPropertyValue( PROPERTY_FORMATSSUPPLIER ) >>= xSupplier;
DBG_ASSERT(xSupplier.is(), "FormComponentPropertyHandler::impl_dialogFormatting_nothrow: invalid call !" );
Reference< XUnoTunnel > xTunnel( xSupplier, UNO_QUERY_THROW );
SvNumberFormatsSupplierObj* pSupplier =
reinterpret_cast< SvNumberFormatsSupplierObj* >( xTunnel->getSomething( SvNumberFormatsSupplierObj::getUnoTunnelId() ) );
DBG_ASSERT( pSupplier != nullptr, "FormComponentPropertyHandler::impl_dialogFormatting_nothrow: invalid call !" );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
sal_Int32 nFormatKey = 0;
impl_getPropertyValue_throw( PROPERTY_FORMATKEY ) >>= nFormatKey;
aCoreSet.Put( SfxUInt32Item( SID_ATTR_NUMBERFORMAT_VALUE, nFormatKey ) );
SvNumberFormatter* pFormatter = pSupplier->GetNumberFormatter();
double dPreviewVal = OFormatSampleControl::getPreviewValue(pFormatter,nFormatKey);
SvxNumberInfoItem aFormatter( pFormatter, dPreviewVal, PcrRes(RID_STR_TEXT_FORMAT).toString(), SID_ATTR_NUMBERFORMAT_INFO );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
aCoreSet.Put( aFormatter );
// a tab dialog with a single page
ScopedVclPtrInstance< SfxSingleTabDialog > xDialog( impl_getDefaultDialogParent_nothrow(), aCoreSet,
"FormatNumberDialog", "cui/ui/formatnumberdialog.ui");
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
SvxAbstractDialogFactory* pFact = SvxAbstractDialogFactory::Create();
DBG_ASSERT( pFact, "CreateFactory fail!" );
::CreateTabPage fnCreatePage = pFact->GetTabPageCreatorFunc( RID_SVXPAGE_NUMBERFORMAT );
if ( !fnCreatePage )
throw RuntimeException(); // caught below
SfxTabPage* pPage = (*fnCreatePage)( xDialog->get_content_area(), &aCoreSet );
xDialog->SetTabPage( pPage );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
_rClearBeforeDialog.clear();
if ( RET_OK == xDialog->Execute() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
const SfxItemSet* pResult = xDialog->GetOutputItemSet();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
const SfxPoolItem* pItem = pResult->GetItem( SID_ATTR_NUMBERFORMAT_INFO );
const SvxNumberInfoItem* pInfoItem = dynamic_cast< const SvxNumberInfoItem* >( pItem );
if (pInfoItem && pInfoItem->GetDelCount())
{
const sal_uInt32* pDeletedKeys = pInfoItem->GetDelArray();
for (sal_uInt32 i=0; i< pInfoItem->GetDelCount(); ++i, ++pDeletedKeys)
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
pFormatter->DeleteEntry(*pDeletedKeys);
}
pItem = nullptr;
if ( SfxItemState::SET == pResult->GetItemState( SID_ATTR_NUMBERFORMAT_VALUE, false, &pItem ) )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
_out_rNewValue <<= (sal_Int32)( static_cast< const SfxUInt32Item* >( pItem )->GetValue() );
bChanged = true;
}
}
}
catch( const Exception& )
{
OSL_FAIL( "FormComponentPropertyHandler::impl_dialogFormatting_nothrow: : caught an exception!" );
DBG_UNHANDLED_EXCEPTION();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
return bChanged;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool FormComponentPropertyHandler::impl_browseForImage_nothrow( Any& _out_rNewValue, ::osl::ClearableMutexGuard& _rClearBeforeDialog ) const
{
bool bIsLink = true;// reflect the legacy behavior
OUString aStrTrans = m_pInfoService->getPropertyTranslation( PROPERTY_ID_IMAGE_URL );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
::sfx2::FileDialogHelper aFileDlg(
ui::dialogs::TemplateDescription::FILEOPEN_LINK_PREVIEW,
SFXWB_GRAPHIC);
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
aFileDlg.SetTitle(aStrTrans);
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
// non-linked images ( e.g. those located in the document
// stream ) only if document is available
bool bHandleNonLink;
{
Reference< XModel > xModel( impl_getContextDocument_nothrow() );
bHandleNonLink = xModel.is();
// Not implemented in reports
if (bHandleNonLink)
{
Reference< XReportDefinition > xReportDef( xModel, css::uno::UNO_QUERY );
bHandleNonLink = !xReportDef.is();
}
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Reference< XFilePickerControlAccess > xController(aFileDlg.GetFilePicker(), UNO_QUERY);
DBG_ASSERT(xController.is(), "FormComponentPropertyHandler::impl_browseForImage_nothrow: missing the controller interface on the file picker!");
if (xController.is())
{
// do a preview by default
xController->setValue(ExtendedFilePickerElementIds::CHECKBOX_PREVIEW, 0, css::uno::Any(true));
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
xController->setValue(ExtendedFilePickerElementIds::CHECKBOX_LINK, 0, css::uno::Any(bIsLink));
xController->enableControl(ExtendedFilePickerElementIds::CHECKBOX_LINK, bHandleNonLink );
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
OUString sCurValue;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( impl_getPropertyValue_throw( PROPERTY_IMAGE_URL ) >>= sCurValue );
if ( !sCurValue.isEmpty() && !sCurValue.startsWith(GRAPHOBJ_URLPREFIX) )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
aFileDlg.SetDisplayDirectory( sCurValue );
// TODO: need to set the display directory _and_ the default name
}
_rClearBeforeDialog.clear();
bool bSuccess = ( 0 == aFileDlg.Execute() );
if ( bSuccess )
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
{
if ( bHandleNonLink && xController.is() )
{
xController->getValue(ExtendedFilePickerElementIds::CHECKBOX_LINK, 0) >>= bIsLink;
}
if ( !bIsLink )
{
Graphic aGraphic;
aFileDlg.GetGraphic( aGraphic );
Reference< graphic::XGraphicObject > xGrfObj = graphic::GraphicObject::create( m_xContext );
xGrfObj->setGraphic( aGraphic.GetXGraphic() );
_out_rNewValue <<= xGrfObj;
}
else
_out_rNewValue <<= aFileDlg.GetPath();
CWS-TOOLING: integrate CWS dba31e 2008-11-19 12:36:23 +0100 msc r263980 : i96104 2008-11-19 12:31:19 +0100 msc r263979 : i96104 2008-11-19 12:21:55 +0100 msc r263977 : i96104 2008-11-19 12:18:53 +0100 msc r263976 : i96104 2008-11-18 09:09:45 +0100 oj r263746 : disable color entry when area is set 2008-11-18 08:37:52 +0100 oj r263741 : #remove sub report entry 2008-11-17 11:20:25 +0100 fs r263708 : #i10000# 2008-11-17 11:06:52 +0100 fs r263706 : minimal version now is 3.1 2008-11-12 22:25:59 +0100 fs r263621 : #i96150# 2008-11-12 22:20:02 +0100 fs r263620 : rebased to m34 2008-11-12 21:39:41 +0100 fs r263618 : MANUAL REBASE: rebase CWS dba31d to DEV300_m34 2008-11-12 13:54:58 +0100 fs r263597 : #i96134# MediaDescriptor.URL is to be preferred over MediaDescriptor.FileName. Nonetheless, ensure both are handled 2008-11-12 13:53:40 +0100 fs r263596 : #i96134# re-enabled the code for #i41897#, a better fix is to come 2008-11-12 12:48:21 +0100 fs r263585 : #i96134# disable saving URLs of file-base databases relatively 2008-11-11 16:11:11 +0100 msc r263566 : #i96104# 2008-11-05 09:09:47 +0100 oj r263342 : #i88727# color noe added 2008-11-05 08:41:43 +0100 oj r263341 : #i77916# zoom added 2008-11-04 21:24:15 +0100 fs r263339 : disposing: call disposeAndClear without own mutex locked - some of our listeners insist on locking the SolarMutex, which sometimes led to deadlocks on the complex test cases 2008-11-04 21:23:15 +0100 fs r263338 : remove SolarMutex locking - this happned in CWS dba31c (in the CVS version), which this CWS was created from, but seems to got lost during resync 2008-11-04 20:49:50 +0100 fs r263335 : docu formatting 2008-11-04 20:06:39 +0100 fs r263334 : #i95826# use m_aMutex, not a DocumentGuard (wrongly resolved merge conflicts) 2008-11-04 17:36:29 +0100 fs r263332 : #i92688# properly revoke as XEventListener from m_xActiveController when disposing 2008-11-04 14:49:34 +0100 fs r263324 : #i92322# enable Input Required if EmptyIsNULL does not exist at the control 2008-10-31 11:10:04 +0100 oj r262857 : merge from cvs to svn 2008-10-31 09:46:45 +0100 oj r262853 : merge from cvs to svn 2008-10-31 08:46:37 +0100 oj r262849 : merge from cvs to svn 2008-10-31 08:44:24 +0100 oj r262848 : merge from cvs to svn 2008-10-31 08:43:33 +0100 oj r262847 : merge from cvs to svn 2008-10-31 08:42:28 +0100 oj r262846 : merge from cvs to svn 2008-10-31 08:41:58 +0100 oj r262845 : merge from cvs to svn 2008-10-31 08:41:32 +0100 oj r262844 : merge from cvs to svn 2008-10-28 12:19:50 +0100 oj r262733 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:42 +0100 oj r262732 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:36 +0100 oj r262731 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:31 +0100 oj r262730 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:22 +0100 oj r262729 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:18 +0100 oj r262728 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:10 +0100 oj r262727 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:06 +0100 oj r262726 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:05 +0100 oj r262725 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:19:01 +0100 oj r262724 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:50 +0100 oj r262723 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:41 +0100 oj r262722 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:40 +0100 oj r262721 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:27 +0100 oj r262720 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:10 +0100 oj r262719 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:18:01 +0100 oj r262718 : #iXXXXX#: migrate CWS dba31e to SVN 2008-10-28 12:17:39 +0100 oj r262717 : #iXXXXX#: migrate CWS dba31e to SVN
2008-12-01 12:31:27 +00:00
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
return bSuccess;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool FormComponentPropertyHandler::impl_browseForTargetURL_nothrow( Any& _out_rNewValue, ::osl::ClearableMutexGuard& _rClearBeforeDialog ) const
{
::sfx2::FileDialogHelper aFileDlg(
ui::dialogs::TemplateDescription::FILEOPEN_READONLY_VERSION, 0);
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OUString sURL;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( impl_getPropertyValue_throw( PROPERTY_TARGET_URL ) >>= sURL );
INetURLObject aParser( sURL );
if ( INetProtocol::File == aParser.GetProtocol() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// set the initial directory only for file-URLs. Everything else
// is considered to be potentially expensive
aFileDlg.SetDisplayDirectory( sURL );
_rClearBeforeDialog.clear();
bool bSuccess = ( 0 == aFileDlg.Execute() );
if ( bSuccess )
_out_rNewValue <<= aFileDlg.GetPath();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
return bSuccess;
}
bool FormComponentPropertyHandler::impl_executeFontDialog_nothrow( Any& _out_rNewValue, ::osl::ClearableMutexGuard& _rClearBeforeDialog ) const
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
bool bSuccess = false;
// create an item set for use with the dialog
SfxItemSet* pSet = nullptr;
SfxItemPool* pPool = nullptr;
SfxPoolItem** pDefaults = nullptr;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
ControlCharacterDialog::createItemSet(pSet, pPool, pDefaults);
ControlCharacterDialog::translatePropertiesToItems(m_xComponent, pSet);
{ // do this in an own block. The dialog needs to be destroyed before we call
// destroyItemSet
ScopedVclPtrInstance< ControlCharacterDialog > aDlg( impl_getDefaultDialogParent_nothrow(), *pSet );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
_rClearBeforeDialog.clear();
if ( RET_OK == aDlg->Execute() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
const SfxItemSet* pOut = aDlg->GetOutputItemSet();
if ( pOut )
{
std::vector< NamedValue > aFontPropertyValues;
ControlCharacterDialog::translateItemsToProperties( *pOut, aFontPropertyValues );
_out_rNewValue <<= comphelper::containerToSequence(aFontPropertyValues);
bSuccess = true;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
ControlCharacterDialog::destroyItemSet(pSet, pPool, pDefaults);
return bSuccess;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool FormComponentPropertyHandler::impl_browseForDatabaseDocument_throw( Any& _out_rNewValue, ::osl::ClearableMutexGuard& _rClearBeforeDialog ) const
{
::sfx2::FileDialogHelper aFileDlg(
ui::dialogs::TemplateDescription::FILEOPEN_READONLY_VERSION, 0,
OUString("sdatabase"));
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OUString sDataSource;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_VERIFY( impl_getPropertyValue_throw( PROPERTY_DATASOURCE ) >>= sDataSource );
INetURLObject aParser( sDataSource );
if ( INetProtocol::File == aParser.GetProtocol() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
// set the initial directory only for file-URLs. Everything else
// is considered to be potentially expensive
aFileDlg.SetDisplayDirectory( sDataSource );
std::shared_ptr<const SfxFilter> pFilter = SfxFilter::GetFilterByName("StarOffice XML (Base)");
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
OSL_ENSURE(pFilter,"Filter: StarOffice XML (Base) could not be found!");
if ( pFilter )
{
CWS-TOOLING: integrate CWS dba31d 2008-12-08 16:22:07 +0100 rt r265005 : Remove DOS lineends 2008-12-05 13:56:24 +0100 fs r264906 : #i10000# removed unreachable statement 2008-11-20 11:41:26 +0100 fs r264037 : merged in the fix for #i95865# (it was wrongly committed to CWS dba32a, should have been here) 2008-11-20 11:34:24 +0100 fs r264036 : line ends 2008-11-14 08:44:50 +0100 lla r263665 : #i10000# comparsion between int and uint fixed 2008-11-13 13:31:12 +0100 lla r263641 : #i10000# build problem fixed 2008-11-13 11:20:01 +0100 lla r263625 : #i96130# hard code name of extension 2008-11-12 11:13:41 +0100 fs r263582 : #i96096# when opening a SRB-report fails due to the missing SRB extension, log this as warning only, and proceed with the migration 2008-11-12 11:11:35 +0100 fs r263581 : #i96096# ContentType handling. Now all contents deliver proper results in XContent::getContentType 2008-11-12 11:10:11 +0100 fs r263580 : #i96096# new ctors taking UNO_QUERY_THROW 2008-11-11 10:10:13 +0100 lla r263546 : CWS-TOOLING: rebase CWS dba31d to trunk@263288 (milestone: DEV300:m35) 2008-11-06 15:55:39 +0100 oj r263393 : #i93452# get field from model fallbackis the name 2008-11-06 15:31:47 +0100 oj r263392 : #i93465# remeber location of floating windows 2008-11-06 13:36:24 +0100 oj r263381 : #i93450# check typemap for null 2008-11-06 13:28:49 +0100 oj r263379 : #i93020# empty column list boxes when new relation should be created 2008-11-06 12:33:53 +0100 oj r263377 : #i93012# set border to default : flat 2008-11-06 12:26:54 +0100 oj r263375 : #i74927# do some less calls for odbc 2008-11-06 09:34:01 +0100 oj r263362 : #i93383# grabFocus in suspend to get allmodified cells 2008-11-03 21:01:39 +0100 oj r263308 : #i86739# check if slash can be valid for tables 2008-11-03 14:40:21 +0100 oj r263287 : #i86739# check if slash can be valid for tables 2008-11-03 14:32:17 +0100 oj r263286 : #i95227# column width 2008-11-03 14:27:26 +0100 oj r263285 : link fwe 2008-11-03 14:24:54 +0100 oj r263284 : #i95235# changed to hold no ref only weak 2008-10-31 11:21:48 +0100 oj r262859 : #i93459# set images add menu entry 2008-10-31 09:06:37 +0100 oj r262851 : #i88629# correct fileopen filter for database odb files 2008-10-30 15:01:04 +0100 oj r262828 : #i95229# set filter at the composer 2008-10-29 15:57:41 +0100 oj r262817 : #i95235# changed to hold no ref only weak 2008-10-29 15:57:19 +0100 oj r262816 : #i95235# changed to hold no ref only weak 2008-10-29 15:57:03 +0100 oj r262815 : #i95235# changed to hold no ref only weak 2008-10-29 15:56:15 +0100 oj r262814 : #i95235# filtermanger changed to hold no ref only weak 2008-10-29 10:32:39 +0100 oj r262773 : #i93474# use correct table name 2008-10-28 13:49:33 +0100 lla r262744 : #i95524# make an Invalidate and refresh on Tables 2008-10-28 10:45:02 +0100 fs r262707 : line ends 2008-10-28 10:34:42 +0100 fs r262706 : #i95522# don't expect the component to live in a TopWindow 2008-10-28 08:30:40 +0100 lla r262696 : #i93176# set preview mode on view 2008-10-28 07:56:57 +0100 oj r262694 : merge cvs svn 2008-10-27 14:13:51 +0100 oj r262673 : #i94129# use dummy data 2008-10-27 12:38:45 +0100 fs r262669 : #i94125# rework ScrollColumns 2008-10-23 15:53:57 +0200 oj r262624 : #i94568# do not load the embeddedobj just copy the storage 2008-10-23 14:39:14 +0200 oj r262622 : #i94129# handle chart correctly 2008-10-22 10:51:19 +0200 lla r262582 : #i94115# problem with left walk chart shape fixed 2008-10-22 07:47:48 +0200 oj r262576 : #i94455# rename now do not use remove insert 2008-10-22 07:47:27 +0200 oj r262575 : #i94455# rename now do not use remove insert 2008-10-21 12:46:26 +0200 lla r262567 : #i93845# extra check if default schema doesn't exists, fix assertion
2008-12-09 07:25:38 +00:00
aFileDlg.SetCurrentFilter(pFilter->GetUIName());
//aFileDlg.AddFilter(pFilter->GetFilterName(),pFilter->GetDefaultExtension());
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
_rClearBeforeDialog.clear();
bool bSuccess = ( 0 == aFileDlg.Execute() );
if ( bSuccess )
_out_rNewValue <<= aFileDlg.GetPath();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
return bSuccess;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool FormComponentPropertyHandler::impl_dialogColorChooser_throw( sal_Int32 _nColorPropertyId, Any& _out_rNewValue, ::osl::ClearableMutexGuard& _rClearBeforeDialog ) const
{
sal_Int32 nColor = 0;
OSL_VERIFY( impl_getPropertyValue_throw( impl_getPropertyNameFromId_nothrow( _nColorPropertyId ) ) >>= nColor );
::Color aColor( nColor );
SvColorDialog aColorDlg( impl_getDefaultDialogParent_nothrow() );
aColorDlg.SetColor( aColor );
_rClearBeforeDialog.clear();
if ( !aColorDlg.Execute() )
return false;
aColor = aColorDlg.GetColor();
nColor = aColor.GetColor();
_out_rNewValue <<= (sal_Int32)nColor;
return true;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool FormComponentPropertyHandler::impl_dialogChooseLabelControl_nothrow( Any& _out_rNewValue, ::osl::ClearableMutexGuard& _rClearBeforeDialog ) const
{
ScopedVclPtrInstance< OSelectLabelDialog > dlgSelectLabel( impl_getDefaultDialogParent_nothrow(), m_xComponent );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
_rClearBeforeDialog.clear();
bool bSuccess = ( RET_OK == dlgSelectLabel->Execute() );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
if ( bSuccess )
_out_rNewValue <<= dlgSelectLabel->GetSelected();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
return bSuccess;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
Reference< XControlContainer > FormComponentPropertyHandler::impl_getContextControlContainer_nothrow() const
{
Reference< XControlContainer > xControlContext;
Any any = m_xContext->getValueByName( "ControlContext" );
any >>= xControlContext;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
return xControlContext;
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
bool FormComponentPropertyHandler::impl_dialogChangeTabOrder_nothrow( ::osl::ClearableMutexGuard& _rClearBeforeDialog ) const
{
OSL_PRECOND( impl_getContextControlContainer_nothrow().is(), "FormComponentPropertyHandler::impl_dialogChangeTabOrder_nothrow: invalid control context!" );
Reference< XTabControllerModel > xTabControllerModel( impl_getRowSet_nothrow(), UNO_QUERY );
ScopedVclPtrInstance<TabOrderDialog> aDialog(
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
impl_getDefaultDialogParent_nothrow(),
xTabControllerModel,
impl_getContextControlContainer_nothrow(),
m_xContext
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
);
_rClearBeforeDialog.clear();
return ( RET_OK == aDialog->Execute() );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
namespace
{
//- ISQLCommandPropertyUI
class ISQLCommandPropertyUI : public ISQLCommandAdapter
{
public:
/** returns the empty-string-terminated list of names of properties
whose UI is to be disabled while the SQL command property is
being edited.
*/
virtual OUString* getPropertiesToDisable() = 0;
};
//- SQLCommandPropertyUI
class SQLCommandPropertyUI : public ISQLCommandPropertyUI
{
protected:
explicit SQLCommandPropertyUI( const Reference< XPropertySet >& _rxObject )
: m_xObject(_rxObject)
{
if ( !m_xObject.is() )
throw NullPointerException();
}
protected:
Reference< XPropertySet > m_xObject;
};
//- FormSQLCommandUI - declaration
class FormSQLCommandUI : public SQLCommandPropertyUI
{
public:
explicit FormSQLCommandUI( const Reference< XPropertySet >& _rxForm );
// ISQLCommandAdapter
virtual OUString getSQLCommand() const override;
virtual bool getEscapeProcessing() const override;
virtual void setSQLCommand( const OUString& _rCommand ) const override;
virtual void setEscapeProcessing( const bool _bEscapeProcessing ) const override;
// ISQLCommandPropertyUI
virtual OUString* getPropertiesToDisable() override;
};
//- FormSQLCommandUI - implementation
FormSQLCommandUI::FormSQLCommandUI( const Reference< XPropertySet >& _rxForm )
:SQLCommandPropertyUI( _rxForm )
{
}
OUString FormSQLCommandUI::getSQLCommand() const
{
OUString sCommand;
OSL_VERIFY( m_xObject->getPropertyValue( PROPERTY_COMMAND ) >>= sCommand );
return sCommand;
}
bool FormSQLCommandUI::getEscapeProcessing() const
{
bool bEscapeProcessing( false );
OSL_VERIFY( m_xObject->getPropertyValue( PROPERTY_ESCAPE_PROCESSING ) >>= bEscapeProcessing );
return bEscapeProcessing;
}
void FormSQLCommandUI::setSQLCommand( const OUString& _rCommand ) const
{
m_xObject->setPropertyValue( PROPERTY_COMMAND, makeAny( _rCommand ) );
}
void FormSQLCommandUI::setEscapeProcessing( const bool _bEscapeProcessing ) const
{
m_xObject->setPropertyValue( PROPERTY_ESCAPE_PROCESSING, makeAny( _bEscapeProcessing ) );
}
OUString* FormSQLCommandUI::getPropertiesToDisable()
{
static OUString s_aCommandProps[] = {
OUString(PROPERTY_DATASOURCE),
OUString(PROPERTY_COMMAND),
OUString(PROPERTY_COMMANDTYPE),
OUString(PROPERTY_ESCAPE_PROCESSING),
OUString()
};
return s_aCommandProps;
}
//- ValueListCommandUI - declaration
class ValueListCommandUI : public SQLCommandPropertyUI
{
public:
explicit ValueListCommandUI( const Reference< XPropertySet >& _rxListOrCombo );
// ISQLCommandAdapter
virtual OUString getSQLCommand() const override;
virtual bool getEscapeProcessing() const override;
virtual void setSQLCommand( const OUString& _rCommand ) const override;
virtual void setEscapeProcessing( const bool _bEscapeProcessing ) const override;
// ISQLCommandPropertyUI
virtual OUString* getPropertiesToDisable() override;
private:
mutable bool m_bPropertyValueIsList;
};
//- ValueListCommandUI - implementation
ValueListCommandUI::ValueListCommandUI( const Reference< XPropertySet >& _rxListOrCombo )
:SQLCommandPropertyUI( _rxListOrCombo )
,m_bPropertyValueIsList( false )
{
}
OUString ValueListCommandUI::getSQLCommand() const
{
OUString sValue;
m_bPropertyValueIsList = false;
// for combo boxes, the property is a mere string
Any aValue( m_xObject->getPropertyValue( PROPERTY_LISTSOURCE ) );
if ( aValue >>= sValue )
return sValue;
Sequence< OUString > aValueList;
if ( aValue >>= aValueList )
{
m_bPropertyValueIsList = true;
if ( aValueList.getLength() )
sValue = aValueList[0];
return sValue;
}
OSL_FAIL( "ValueListCommandUI::getSQLCommand: unexpected property type!" );
return sValue;
}
bool ValueListCommandUI::getEscapeProcessing() const
{
enum ListSourceType eType( ListSourceType_SQL );
OSL_VERIFY( m_xObject->getPropertyValue( PROPERTY_LISTSOURCETYPE ) >>= eType );
OSL_ENSURE( ( eType == ListSourceType_SQL ) || ( eType == ListSourceType_SQLPASSTHROUGH ),
"ValueListCommandUI::getEscapeProcessing: unexpected list source type!" );
return ( eType == ListSourceType_SQL );
}
void ValueListCommandUI::setSQLCommand( const OUString& _rCommand ) const
{
Any aValue;
if ( m_bPropertyValueIsList )
aValue <<= Sequence< OUString >( &_rCommand, 1 );
else
aValue <<= _rCommand;
m_xObject->setPropertyValue( PROPERTY_LISTSOURCE, aValue );
}
void ValueListCommandUI::setEscapeProcessing( const bool _bEscapeProcessing ) const
{
m_xObject->setPropertyValue( PROPERTY_LISTSOURCETYPE, makeAny(
_bEscapeProcessing ? ListSourceType_SQL : ListSourceType_SQLPASSTHROUGH ) );
}
OUString* ValueListCommandUI::getPropertiesToDisable()
{
static OUString s_aListSourceProps[] = {
OUString(PROPERTY_LISTSOURCETYPE),
OUString(PROPERTY_LISTSOURCE),
OUString()
};
return s_aListSourceProps;
}
}
bool FormComponentPropertyHandler::impl_doDesignSQLCommand_nothrow( const Reference< XObjectInspectorUI >& _rxInspectorUI, PropertyId _nDesignForProperty )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
try
{
if ( m_xCommandDesigner.is() )
{
if ( m_xCommandDesigner->isActive() )
{
m_xCommandDesigner->raise();
return true;
}
m_xCommandDesigner->dispose();
m_xCommandDesigner.set( nullptr );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
if ( !impl_ensureRowsetConnection_nothrow() )
return false;
Reference< XPropertySet > xComponentProperties( m_xComponent, UNO_QUERY_THROW );
::rtl::Reference< ISQLCommandPropertyUI > xCommandUI;
switch ( _nDesignForProperty )
{
case PROPERTY_ID_COMMAND:
xCommandUI = new FormSQLCommandUI( xComponentProperties );
break;
case PROPERTY_ID_LISTSOURCE:
xCommandUI = new ValueListCommandUI( xComponentProperties );
break;
default:
OSL_FAIL( "FormComponentPropertyHandler::OnDesignerClosed: invalid property id!" );
return false;
}
m_xCommandDesigner.set( new SQLCommandDesigner( m_xContext, xCommandUI.get(), m_xRowSetConnection, LINK( this, FormComponentPropertyHandler, OnDesignerClosed ) ) );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
DBG_ASSERT( _rxInspectorUI.is(), "FormComponentPropertyHandler::OnDesignerClosed: no access to the property browser ui!" );
if ( m_xCommandDesigner->isActive() && _rxInspectorUI.is() )
{
m_xBrowserUI = _rxInspectorUI;
// disable everything which would affect this property
const OUString* pToDisable = xCommandUI->getPropertiesToDisable();
while ( !pToDisable->isEmpty() )
{
m_xBrowserUI->enablePropertyUIElements( *pToDisable++, PropertyLineElement::All, sal_False );
}
// but enable the browse button for the property itself - so it can be used to raise the query designer
OUString sPropertyName( impl_getPropertyNameFromId_nothrow( _nDesignForProperty ) );
m_xBrowserUI->enablePropertyUIElements( sPropertyName, PropertyLineElement::PrimaryButton, sal_True );
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
catch( const Exception& )
{
DBG_UNHANDLED_EXCEPTION();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
return m_xCommandDesigner.is();
}
IMPL_LINK_NOARG_TYPED( FormComponentPropertyHandler, OnDesignerClosed, SQLCommandDesigner&, void )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
OSL_ENSURE( m_xBrowserUI.is() && m_xCommandDesigner.is(), "FormComponentPropertyHandler::OnDesignerClosed: too many NULLs!" );
if ( m_xBrowserUI.is() && m_xCommandDesigner.is() )
{
try
{
::rtl::Reference< ISQLCommandPropertyUI > xCommandUI(
dynamic_cast< ISQLCommandPropertyUI* >( m_xCommandDesigner->getPropertyAdapter().get() ) );
if ( !xCommandUI.is() )
throw NullPointerException();
const OUString* pToEnable = xCommandUI->getPropertiesToDisable();
while ( !pToEnable->isEmpty() )
{
m_xBrowserUI->enablePropertyUIElements( *pToEnable++, PropertyLineElement::All, sal_True );
}
}
catch( const Exception& )
{
DBG_UNHANDLED_EXCEPTION();
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
bool FormComponentPropertyHandler::impl_hasValidDataSourceSignature_nothrow( const Reference< XPropertySet >& _xFormProperties, bool _bAllowEmptyDataSourceName )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
bool bHas = false;
if ( _xFormProperties.is() )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
try
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
OUString sPropertyValue;
// first, we need the name of an existent data source
if ( _xFormProperties->getPropertySetInfo()->hasPropertyByName(PROPERTY_DATASOURCE) )
_xFormProperties->getPropertyValue( PROPERTY_DATASOURCE ) >>= sPropertyValue;
bHas = ( !sPropertyValue.isEmpty() ) || _bAllowEmptyDataSourceName;
// then, the command should not be empty
if ( bHas )
{
if ( _xFormProperties->getPropertySetInfo()->hasPropertyByName(PROPERTY_COMMAND) )
_xFormProperties->getPropertyValue( PROPERTY_COMMAND ) >>= sPropertyValue;
bHas = !sPropertyValue.isEmpty();
}
}
catch( const Exception& )
{
OSL_FAIL( "FormComponentPropertyHandler::impl_hasValidDataSourceSignature_nothrow: caught an exception!" );
DBG_UNHANDLED_EXCEPTION();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
}
return bHas;
}
OUString FormComponentPropertyHandler::impl_getDocumentURL_nothrow() const
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
OUString sURL;
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
try
{
Reference< XModel > xDocument( impl_getContextDocument_nothrow() );
if ( xDocument.is() )
sURL = xDocument->getURL();
}
catch( const Exception& )
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
{
DBG_UNHANDLED_EXCEPTION();
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
}
return sURL;
}
::cppu::IPropertyArrayHelper* FormComponentPropertyHandler::createArrayHelper( ) const
{
uno::Sequence< beans::Property > aProps;
describeProperties(aProps);
return new ::cppu::OPropertyArrayHelper(aProps);
}
::cppu::IPropertyArrayHelper & FormComponentPropertyHandler::getInfoHelper()
{
return *getArrayHelper();
}
uno::Reference< beans::XPropertySetInfo > SAL_CALL FormComponentPropertyHandler::getPropertySetInfo( ) throw(uno::RuntimeException, std::exception)
{
return ::cppu::OPropertySetHelper::createPropertySetInfo(getInfoHelper());
}
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
} // namespace pcr
INTEGRATION: CWS pbrwuno (1.1.2); FILE ADDED 2006/03/09 13:22:52 fs 1.1.2.33: #i62965# release own mutex before executing a modal dialog 2006/03/08 10:12:20 fs 1.1.2.32: varname typo 2006/03/07 20:01:33 fs 1.1.2.31: properly en/disable TARGET_FRAME, also for forms 2006/02/15 07:25:53 fs 1.1.2.30: don't access &(*foo.begin()) of empty STL containers 2006/02/10 07:53:48 fs 1.1.2.29: manual RESYNC to m156 2005/11/02 12:17:16 fs 1.1.2.28: #i10000# exception specifications 2005/11/02 11:43:42 fs 1.1.2.27: #i10000# exception specifications 2005/10/31 13:45:57 fs 1.1.2.26: some cleanup 2005/10/26 14:49:34 fs 1.1.2.25: #i53095# 2005/10/26 14:03:32 fs 1.1.2.24: some cleanups for finalizing #i53095# 2005/10/25 12:23:00 fs 1.1.2.23: misc cleanup 2005/10/25 11:52:41 fs 1.1.2.22: #i53095# some exception specifications, and some conceptual changes for multiple handlers supporting the same property 2005/10/25 07:13:10 fs 1.1.2.21: #i53095# knitting lose ends (amongst others, make the handlers available as service) 2005/10/24 08:41:47 fs 1.1.2.20: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.* 2005/10/17 14:09:19 fs 1.1.2.19: #i53095# some cleanup of remaining TODOs 2005/10/17 13:19:00 fs 1.1.2.18: #i53095# proper listener administration: allow multiple listeners per handler 2005/10/17 10:27:59 fs 1.1.2.17: #i53095# make numeric field exchange its values as double 2005/10/17 09:48:36 fs 1.1.2.16: #i53095# make DateFields and TimeFields exchange their values as css.util.Date/Time 2005/10/17 08:58:17 fs 1.1.2.15: some mutex locking 2005/10/17 08:38:37 fs 1.1.2.14: implement auto-firing for ComposedUIUpdate 2005/10/17 08:17:00 fs 1.1.2.13: #i53095# 2005/10/17 07:17:03 fs 1.1.2.12: replace MeasurementUnit with css.util.MeasureUnit 2005/10/14 12:43:45 fs 1.1.2.11: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values 2005/10/14 08:40:43 fs 1.1.2.10: #i53095# let the XObjectInspectorModel provide category meta information part 2005/10/13 13:01:02 fs 1.1.2.9: #i53095# introduce an XObjectInspector/Model 2005/10/11 13:29:13 fs 1.1.2.8: #i53095# phase 3: introduced XPropertyHandler and XObjectInspectorUI same open issues as in previous phase (plus probably some more, since not everything is tested, yet :-\) 2005/10/07 12:25:14 fs 1.1.2.7: #i53095# also set the HasFooButton properties at the descriptor 2005/09/05 07:41:49 fs 1.1.2.6: #i53095# phase 3, part 1: introduced XPropertyControl and relatives, describing one control in the ObjectInspector, responsible for one property known issues: - rebuildPropertyUI can cause problems now: If the user clicks into the control for property A, which causes property B to be committed, which causes the UI for property A to be rebuilt, then this will crash currently. Reason: rebuildPropertyUI now synchronously replaces the VCL-Window of the rebuilt control, which is exactly the one which is still in some MouseButtonDown-handler. possible solutions: - see if rebuiltPropertyUI can be obsoleted - handlers should be able to just obtain the XPropertyControl from the PropertyUI, and re-initialize the control. Shouldn't they?` - make one of the steps in the chain (mouse-click, handler-call, rebuildPropertyUI-callback) asynchronous. 2005/08/18 12:44:28 fs 1.1.2.5: #i53095#, phase 2 moved (nearly) all property handling to dedicated handlers, the controller is now simply managing a set of handlers open issues for making the property browser completely generic: - target page for a property - at the moment, the pbrw uses form-specific knowledge - relative position of properties. Again, the pbrw uses the OPropertyInfoService which is not generic - isComposeable for a given property. Also OPropertyInfoService-dependent ATM - help ids of pages and the pbrw as a whole. They're hard-coded at the moment other open issues: everything in the code which is tagged with TOD/UNOize. Those are items which do not immediately hinder phase 3 (real UNOization, i.e. definition of new UNO interfaces for the handlers, the controller, and so on), but need to be addressed in phase 4 (knit lose ends) 2005/08/16 05:39:00 fs 1.1.2.4: #i53095# completely moved the handling of actuating properties into dedicated handlers 2005/08/12 16:30:10 fs 1.1.2.3: - more fine-grained control in the IPropertyBrowserUI which elements to enable or disable - moved designing the SQL command into a dedicated handler - some more reactions on actuating properties move to dedicated handlers - *nearly* completed implementation of the "composed browser UI", which collects and combines UI change requests (IPropertyBrowserUI) (still missing: proper auto-firing) 2005/08/10 15:41:44 fs 1.1.2.2: #i53095# get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked, and move them to a FormComponentHandler [1] still to migrate: - browsing for events (needs a dedicated event property handler) - handling for clicking the button of the Command property - this is kind of asynchronous, and IPropertyHandler is not yet prepared for this 2005/08/09 13:59:59 fs 1.1.2.1: #i53095# phase 1: - don't use strings to transver values between controls and introspectee, but Anys - first version of a dedicated property handler for form-component-related properties (not yet completed) known regressions over previous phase: - handlers for events not yet implemented, thus some assertions - click handlers for form-component-related properties do not yet work, thus the browse buttons mostly do not work
2006-03-14 10:23:06 +00:00
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */