2010-10-27 12:45:03 +01:00
|
|
|
/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
|
re-base on ALv2 code. Includes (at least) relevant parts of:
linecap: Reintegrating finished LineCap feature
Patch contributed by Regina Henschel
http://svn.apache.org/viewvc?view=revision&revision=1232507
Patches contributed by Sven Jacobi
impress212: #i81610# fixed animation export
http://svn.apache.org/viewvc?view=revision&revision=1167620
impress212: drawinglayer gbuild environment changes
http://svn.apache.org/viewvc?view=revision&revision=1167627
http://svn.apache.org/viewvc?view=revision&revision=1167628
impress212: DffPropSet -> minor code improvements, removing table
http://svn.apache.org/viewvc?view=revision&revision=1167634
impress212: #158494# fixed excel import (text rotation)
http://svn.apache.org/viewvc?view=revision&revision=1167638
Patches contributed by Armin Le Grand
Svg: Reintegrated Svg replacement from /branches/alg/svgreplavement
http://svn.apache.org/viewvc?view=revision&revision=1220836
#118728# changed indentifying definitions for Svg file detection
http://svn.apache.org/viewvc?view=revision&revision=1229961
#118838# LineGeometry creation for complicated cases optimized to
create single Polygons
http://svn.apache.org/viewvc?view=revision&revision=1236232
#119176# corrected file type detection for SVG for svg files
without xml header
http://svn.apache.org/viewvc?view=revision&revision=1309445
#118728# Extended Svg file detection
http://svn.apache.org/viewvc?view=revision&revision=1230531
#118529# solve break converters and convert commands for OLEs and images
http://svn.apache.org/viewvc?view=revision&revision=1186168
svg: added WaE changes from branch svgreplacement to trunc
http://svn.apache.org/viewvc?view=revision&revision=1222974
svg: corrected missing member initialization
http://svn.apache.org/viewvc?view=revision&revision=1226134
fix for #118525#: Using primitives for chart sub-geometry visualisation
http://svn.apache.org/viewvc?view=revision&revision=1226879
#118898# Adapted ImpGraphic::ImplGetBitmap to correctly convert
metafiles to bitmapEx ...
http://svn.apache.org/viewvc?view=revision&revision=1293316
fix for #118525#: removed no longer used variable maOriginalMapMode, one
more exception eliminated
http://svn.apache.org/viewvc?view=revision&revision=1227097
#16758# Added buffering to the VDev usages of the VclProcessor2D derivates...
http://svn.apache.org/viewvc?view=revision&revision=1229521
#116758# Secured VDev buffer device to Vcl deinit
http://svn.apache.org/viewvc?view=revision&revision=1230574
#116758# added remembering allocated VDevs for VDevBuffer to be able to also
delete these when vcl goes down; it should never happen, but You never know
http://svn.apache.org/viewvc?view=revision&revision=1230927
#118730# Changed SvgClipPathNode to use MaskPrimitive2D for primitive
representation instead of TransparencePrimitive2D
http://svn.apache.org/viewvc?view=revision&revision=1231198
#118822# secured 3D geometry creation (slices) by subdividing the 2D
source polyPolygon early
http://svn.apache.org/viewvc?view=revision&revision=1234749
#118829# enhanced Svg gradient quality, obstacles avoided
http://svn.apache.org/viewvc?view=revision&revision=1235361
#118834# Unified usage of TextBreakupHelper as single tooling class
for i18n text primitive breakup
http://svn.apache.org/viewvc?view=revision&revision=1236110
#118853# added square pixel size limit to conversion of
TransparencePrimitive2D to Metafile action
http://svn.apache.org/viewvc?view=revision&revision=1237656
#118824# coreccted mirroring and boundrect when the graphicmanager
is used for bitmap output
http://svn.apache.org/viewvc?view=revision&revision=1240097
#115092# Corrected VclProcessor2D::RenderPolygonStrokePrimitive2D for
various optimization scenarios
http://svn.apache.org/viewvc?view=revision&revision=1241434
#118783# Corrected errors in ID strings, corrected Svg line/fill export,
corrected polygon close state
http://svn.apache.org/viewvc?view=revision&revision=1232006
#118796# corrected null-pointer usage in SVG text exporter
http://svn.apache.org/viewvc?view=revision&revision=1240262
#118729# Use GraphicStreamUrl and GraphicUrl to allow multi image
import with linked graphics, too
http://svn.apache.org/viewvc?view=revision&revision=1229962
#118898# corrected error in GDIMetaFile::GetBoundRect in handling
MetaFloatTransparentAction
http://svn.apache.org/viewvc?view=revision&revision=1293349
#118855# Corrected handling of possibly created empty clipRegions
after PolyPolygon clipping
http://svn.apache.org/viewvc?view=revision&revision=1237725
#115962# Better (but not yet optimal, see comments in task) handling
of MetaFloatTransparentAction in PDF export
http://svn.apache.org/viewvc?view=revision&revision=1241078
IP clearance: #118466# This patch removes librsvg, libcroco, libgsf, ...
http://svn.apache.org/viewvc?view=revision&revision=1200879
118779# Added svg content streaming in/out to ImpGraphic stream operators
http://svn.apache.org/viewvc?view=revision&revision=1231908
linecap: correctons for WaE and mac drawing
http://svn.apache.org/viewvc?view=revision&revision=1232793
svg: uses current system Dpi for Svg replacement image creation
http://svn.apache.org/viewvc?view=revision&revision=1233948
Patches contributed by Mathias Bauer (and others)
gnumake4 work variously
http://svn.apache.org/viewvc?view=revision&revision=1394326
http://svn.apache.org/viewvc?view=revision&revision=1396797
http://svn.apache.org/viewvc?view=revision&revision=1397315
http://svn.apache.org/viewvc?view=revision&revision=1394326
Remove duplicate header includes.
cws mba34issues01: #i117720#: convert assertion into warning
http://svn.apache.org/viewvc?view=revision&revision=1172352
118485 - Styles for OLEs are not saved. Submitted by Armin Le Grand.
http://svn.apache.org/viewvc?view=revision&revision=1182166
cws mba34issues01: #i117714#: remove assertion
http://svn.apache.org/viewvc?view=revision&revision=1172357
Patch contributed by Jurgen Schmidt
add some additional checks to ensure proper reading operations
http://svn.apache.org/viewvc?view=revision&revision=1209022
mostly prefer our stream / bounds checking work.
Patches contributed by Herbert Duerr
#i118816# add clarifying comment regarding Font::*Color*() methods
http://svn.apache.org/viewvc?view=revision&revision=1233833
extend macro->string handling for empty strings
http://svn.apache.org/viewvc?view=revision&revision=1175801
avoid magic constants for SALCOLOR_NONE
http://svn.apache.org/viewvc?view=revision&revision=1177543
initialize slant properly in ImplFontMetricData constructor (author=iorsh)
http://svn.apache.org/viewvc?view=revision&revision=1177551
#i118675# make check for extension updates more stable
http://svn.apache.org/viewvc?view=revision&revision=1214797
#a118617# remove VBasicEventListener.dll binary
There are no known users depending on its CLSID
http://svn.apache.org/viewvc?view=revision&revision=1203697
Patches contributed by Ariel Constenla-Haile
Fix build breaker on Linux/gcc
http://svn.apache.org/viewvc?view=revision&revision=1221104
Fix crash when trying to instantiate css.graphic.GraphicRasterizer_RSVG
http://svn.apache.org/viewvc?view=revision&revision=1215559
Patches contributed by Oliver-Rainer Wittmann
sw34bf06: #i117962# - method <SwFlyFrm::IsPaint(..)> - consider
instances of <SwFlyDrawObj>
http://svn.apache.org/viewvc?view=revision&revision=1172120
sw34bf06: #i117783# - Writer's implementation of XPagePrintable -
apply print settings to new printing routines
http://svn.apache.org/viewvc?view=revision&revision=1172115
gnumake4 work variously from Hans-Joachim Lankenau
http://svn.apache.org/viewvc?view=revision&revision=1397315
http://svn.apache.org/viewvc?view=revision&revision=1396797
http://svn.apache.org/viewvc?view=revision&revision=1396782
http://svn.apache.org/viewvc?view=revision&revision=1394707
plus some amount of re-splitting of legacy headers.
Patch contributed by Pavel Janik
WaE: Remove unused variables.
http://svn.apache.org/viewvc?view=revision&revision=1230697
Patches contributed by Takashi Ono
mingwport35: i#117795: MinGW port fix for vcl2gnumake
http://svn.apache.org/viewvc?view=revision&revision=1172091
mingwport35: i#117795: MinGW port fix for vcl2gnumake
http://svn.apache.org/viewvc?view=revision&revision=1172091
Patch contributed by Christian Lippka
impress212: #i98044# re enable Text menu for outline and title shapes
http://svn.apache.org/viewvc?view=revision&revision=1167639
Patch contributed by Andre Fischer
118674: Made category B code optional and disabled by default.
http://svn.apache.org/viewvc?view=revision&revision=1215131
118881: Ignore empty paragraphs after bullets.
http://svn.apache.org/viewvc?view=revision&revision=1296205
Patches contributed by Philipp Lohmann
ooo340fixes: #i117780# use rtl allocator
http://svn.apache.org/viewvc?view=revision&revision=1172087
ooo34gsl02: #i117807# fix an off by one error (index actually
inside the pfb section header)
http://svn.apache.org/viewvc?view=revision&revision=1167576
various cleanups, related compilation fixes, warning cleanups, re-working
of obsolete stl template pieces to use boost instead, changed string
classes, re-adapt KDE about data, about dialog, fixing warnings,
and other fixes & improvements.
Disable svg import / render for about/ branding code-paths for now.
Restore full icon theme set.
Remove OS/2 conditionals and sources.
Remove conflicting gtk/full-screen monitors support.
Retain existing svg rasterizer files - temporarily disabled.
Standardize stringificaiton and fixup dllpostfix issues.
Rename SvgGradientHelper::== to equalTo to avoid overloading issues.
Use the flat GdiPlus API for LineCaps calls.
2012-10-09 12:22:23 +01:00
|
|
|
/*
|
|
|
|
* This file is part of the LibreOffice project.
|
|
|
|
*
|
|
|
|
* This Source Code Form is subject to the terms of the Mozilla Public
|
|
|
|
* License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
|
|
* file, You can obtain one at http://mozilla.org/MPL/2.0/.
|
|
|
|
*
|
|
|
|
* This file incorporates work covered by the following license notice:
|
|
|
|
*
|
|
|
|
* Licensed to the Apache Software Foundation (ASF) under one or more
|
|
|
|
* contributor license agreements. See the NOTICE file distributed
|
|
|
|
* with this work for additional information regarding copyright
|
|
|
|
* ownership. The ASF licenses this file to you under the Apache
|
|
|
|
* License, Version 2.0 (the "License"); you may not use this file
|
|
|
|
* except in compliance with the License. You may obtain a copy of
|
|
|
|
* the License at http://www.apache.org/licenses/LICENSE-2.0 .
|
|
|
|
*/
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-04-18 20:41:29 +02:00
|
|
|
#ifndef INCLUDED_EXTENSIONS_SOURCE_PROPCTRLR_BROWSERLISTBOX_HXX
|
|
|
|
#define INCLUDED_EXTENSIONS_SOURCE_PROPCTRLR_BROWSERLISTBOX_HXX
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
#include "browserline.hxx"
|
|
|
|
#include "modulepcr.hxx"
|
|
|
|
#include "pcrcommon.hxx"
|
|
|
|
|
|
|
|
#include <com/sun/star/inspection/XPropertyControl.hpp>
|
|
|
|
#include <com/sun/star/inspection/XPropertyHandler.hpp>
|
2001-01-12 10:35:45 +00:00
|
|
|
#include <vcl/scrbar.hxx>
|
|
|
|
#include <vcl/lstbox.hxx>
|
|
|
|
#include <vcl/button.hxx>
|
|
|
|
#include <tools/link.hxx>
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
#include <rtl/ref.hxx>
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2015-09-18 11:51:16 +01:00
|
|
|
#include <memory>
|
2004-11-16 11:01:00 +00:00
|
|
|
#include <set>
|
2015-01-04 11:10:45 +00:00
|
|
|
#include <unordered_map>
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
#include <vector>
|
2004-11-16 11:01:00 +00:00
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
namespace pcr
|
|
|
|
{
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
|
|
|
|
class IPropertyLineListener;
|
2006-12-13 10:55:49 +00:00
|
|
|
class IPropertyControlObserver;
|
2001-01-12 10:35:45 +00:00
|
|
|
struct OLineDescriptor;
|
2006-12-13 10:55:49 +00:00
|
|
|
class InspectorHelpWindow;
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
class PropertyControlContext_Impl;
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2015-05-15 13:27:19 +02:00
|
|
|
// administrative structures for OBrowserListBox
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2015-09-18 11:51:16 +01:00
|
|
|
typedef std::shared_ptr< OBrowserLine > BrowserLinePointer;
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
struct ListBoxLine
|
|
|
|
{
|
2013-04-07 12:06:47 +02:00
|
|
|
OUString aName;
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
BrowserLinePointer pLine;
|
2015-09-30 11:48:44 +02:00
|
|
|
css::uno::Reference< css::inspection::XPropertyHandler >
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
xHandler;
|
|
|
|
|
2016-08-18 12:27:49 +01:00
|
|
|
ListBoxLine( const OUString& rName, const BrowserLinePointer& _pLine, const css::uno::Reference< css::inspection::XPropertyHandler >& _rxHandler )
|
2012-02-10 14:12:17 +01:00
|
|
|
: aName( rName ),
|
|
|
|
pLine( _pLine ),
|
|
|
|
xHandler( _rxHandler )
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
{
|
|
|
|
}
|
|
|
|
};
|
2012-02-10 14:12:17 +01:00
|
|
|
typedef ::std::vector< ListBoxLine > ListBoxLines;
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
class OBrowserListBox :public Control
|
|
|
|
,public IButtonClickListener
|
|
|
|
,public PcrClient
|
2001-01-12 10:35:45 +00:00
|
|
|
{
|
|
|
|
protected:
|
2015-01-26 13:11:07 +02:00
|
|
|
VclPtr<Window> m_aLinesPlayground;
|
|
|
|
VclPtr<ScrollBar> m_aVScroll;
|
2015-03-16 12:17:44 +02:00
|
|
|
VclPtr<InspectorHelpWindow> m_pHelpWindow;
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
ListBoxLines m_aLines;
|
2001-01-12 10:35:45 +00:00
|
|
|
IPropertyLineListener* m_pLineListener;
|
2006-12-13 10:55:49 +00:00
|
|
|
IPropertyControlObserver* m_pControlObserver;
|
2001-01-12 10:35:45 +00:00
|
|
|
long m_nYOffset;
|
2006-12-13 10:55:49 +00:00
|
|
|
long m_nCurrentPreferredHelpHeight;
|
2015-09-30 11:48:44 +02:00
|
|
|
css::uno::Reference< css::inspection::XPropertyControl >
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
m_xActiveControl;
|
2001-01-12 10:35:45 +00:00
|
|
|
sal_uInt16 m_nTheNameSize;
|
2014-06-17 12:04:10 +01:00
|
|
|
long m_nRowHeight;
|
2004-11-16 11:01:00 +00:00
|
|
|
::std::set< sal_uInt16 > m_aOutOfDateLines;
|
2014-04-30 11:46:15 +02:00
|
|
|
bool m_bIsActive : 1;
|
|
|
|
bool m_bUpdate : 1;
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
::rtl::Reference< PropertyControlContext_Impl >
|
|
|
|
m_pControlContextImpl;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
|
|
|
protected:
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
void PositionLine( sal_uInt16 _nIndex );
|
|
|
|
void UpdatePosNSize();
|
|
|
|
void UpdatePlayGround();
|
|
|
|
void UpdateVScroll();
|
|
|
|
void ShowEntry(sal_uInt16 nPos);
|
2006-03-31 08:24:18 +00:00
|
|
|
void MoveThumbTo(sal_Int32 nNewThumbPos);
|
2015-10-12 16:04:04 +02:00
|
|
|
void Resize() override;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
|
|
|
public:
|
2016-11-01 11:44:15 +01:00
|
|
|
explicit OBrowserListBox( vcl::Window* pParent );
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2016-09-13 13:09:01 +02:00
|
|
|
virtual ~OBrowserListBox() override;
|
2015-10-12 16:04:04 +02:00
|
|
|
virtual void dispose() override;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-04-30 11:46:15 +02:00
|
|
|
void ActivateListBox( bool _bActive );
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
sal_uInt16 CalcVisibleLines();
|
|
|
|
void EnableUpdate();
|
|
|
|
void DisableUpdate();
|
2016-11-24 22:40:33 +01:00
|
|
|
bool EventNotify( NotifyEvent& _rNEvt ) override;
|
2015-10-12 16:04:04 +02:00
|
|
|
virtual bool PreNotify( NotifyEvent& _rNEvt ) override;
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2006-12-13 10:55:49 +00:00
|
|
|
void SetListener( IPropertyLineListener* _pListener );
|
|
|
|
void SetObserver( IPropertyControlObserver* _pObserver );
|
|
|
|
|
|
|
|
void EnableHelpSection( bool _bEnable );
|
|
|
|
bool HasHelpSection() const;
|
2013-04-07 12:06:47 +02:00
|
|
|
void SetHelpText( const OUString& _rHelpText );
|
2006-12-13 10:55:49 +00:00
|
|
|
void SetHelpLineLimites( sal_Int32 _nMinLines, sal_Int32 _nMaxLines );
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
void Clear();
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2016-08-05 11:11:03 +02:00
|
|
|
void InsertEntry( const OLineDescriptor&, sal_uInt16 nPos );
|
2015-09-30 11:48:44 +02:00
|
|
|
bool RemoveEntry( const OUString& _rName );
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
void ChangeEntry( const OLineDescriptor&, sal_uInt16 nPos );
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2015-09-30 11:48:44 +02:00
|
|
|
void SetPropertyValue( const OUString& rEntryName, const css::uno::Any& rValue, bool _bUnknownValue );
|
2013-04-07 12:06:47 +02:00
|
|
|
sal_uInt16 GetPropertyPos( const OUString& rEntryName ) const;
|
2015-09-30 11:48:44 +02:00
|
|
|
css::uno::Reference< css::inspection::XPropertyControl >
|
2013-04-07 12:06:47 +02:00
|
|
|
GetPropertyControl( const OUString& rEntryName );
|
|
|
|
void EnablePropertyControls( const OUString& _rEntryName, sal_Int16 _nControls, bool _bEnable );
|
|
|
|
void EnablePropertyLine( const OUString& _rEntryName, bool _bEnable );
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
sal_Int32 GetMinimumWidth();
|
2006-12-13 10:55:49 +00:00
|
|
|
sal_Int32 GetMinimumHeight();
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2002-11-06 08:20:07 +00:00
|
|
|
|
2015-10-12 14:35:25 +02:00
|
|
|
bool IsModified( ) const;
|
|
|
|
void CommitModified( );
|
2002-11-06 08:20:07 +00:00
|
|
|
|
2017-01-19 17:57:50 +01:00
|
|
|
/// @throws css::uno::RuntimeException
|
2015-10-12 14:35:25 +02:00
|
|
|
void SAL_CALL focusGained( const css::uno::Reference< css::inspection::XPropertyControl >& Control ) throw (css::uno::RuntimeException);
|
2017-01-19 17:57:50 +01:00
|
|
|
/// @throws css::uno::RuntimeException
|
2015-10-12 14:35:25 +02:00
|
|
|
void SAL_CALL valueChanged( const css::uno::Reference< css::inspection::XPropertyControl >& Control ) throw (css::uno::RuntimeException);
|
2017-01-19 17:57:50 +01:00
|
|
|
/// @throws css::uno::RuntimeException
|
2015-10-12 14:35:25 +02:00
|
|
|
void SAL_CALL activateNextControl( const css::uno::Reference< css::inspection::XPropertyControl >& CurrentControl ) throw (css::uno::RuntimeException);
|
2003-03-25 15:04:55 +00:00
|
|
|
|
2015-10-12 14:35:25 +02:00
|
|
|
protected:
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
// IButtonClickListener
|
2015-10-12 16:04:04 +02:00
|
|
|
void buttonClicked( OBrowserLine* _pLine, bool _bPrimary ) override;
|
2003-03-25 15:04:55 +00:00
|
|
|
|
2008-01-14 13:56:11 +00:00
|
|
|
using Window::SetHelpText;
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
private:
|
2016-10-05 07:56:12 +02:00
|
|
|
DECL_LINK( ScrollHdl, ScrollBar*, void );
|
2001-01-12 10:35:45 +00:00
|
|
|
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
/** retrieves the index of a given control in our line list
|
|
|
|
@param _rxControl
|
|
|
|
The control to lookup. Must denote a control of one of the lines in ->m_aLines
|
|
|
|
*/
|
2015-09-30 11:48:44 +02:00
|
|
|
sal_uInt16 impl_getControlPos( const css::uno::Reference< css::inspection::XPropertyControl >& _rxControl ) const;
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
|
|
|
|
/** sets the given property value at the given control, after converting it as necessary
|
|
|
|
@param _rLine
|
|
|
|
The line whose at which the value is to be set.
|
|
|
|
@param _rPropertyValue
|
|
|
|
the property value to set. If it's not compatible with the control value,
|
|
|
|
it will be converted, using <member>XPropertyHandler::convertToControlValue</member>
|
|
|
|
*/
|
2015-09-30 11:48:44 +02:00
|
|
|
static void impl_setControlAsPropertyValue( const ListBoxLine& _rLine, const css::uno::Any& _rPropertyValue );
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
|
|
|
|
/** retrieves the value for the given control, as a property value, after converting it as necessary
|
|
|
|
@param _rLine
|
|
|
|
The line whose at which the value is to be set.
|
|
|
|
*/
|
2015-09-30 11:48:44 +02:00
|
|
|
static css::uno::Any
|
2015-04-15 13:17:16 +02:00
|
|
|
impl_getControlAsPropertyValue( const ListBoxLine& _rLine );
|
INTEGRATION: CWS pbrwuno (1.6.156); FILE MERGED
2005/10/24 08:41:37 fs 1.6.156.11: start making the handlers full-fledged components, with using a new infrastructure replacing extensions/source/inc/componentmodule.*
2005/10/19 07:48:04 fs 1.6.156.10: #i53095# knitting some loose ends
2005/10/14 12:43:44 fs 1.6.156.9: #i53095# properly care for MAYBEVOID properties and AMBIGUOUS property values
2005/10/11 13:28:46 fs 1.6.156.8: #i53095# phase 3:
introduced XPropertyHandler and XObjectInspectorUI
same open issues as in previous phase
(plus probably some more, since not everything is tested, yet :-\)
2005/10/07 12:24:19 fs 1.6.156.7: #i53095# notifications to the IControlContext are asynchronous now - this prevents problems if such a notification causes the exchange of control/windows
2005/10/05 06:49:24 fs 1.6.156.6: RESYNC: (1.6-1.7); FILE MERGED
2005/09/05 07:41:47 fs 1.6.156.5: #i53095# phase 3, part 1: introduced XPropertyControl and relatives,
describing one control in the ObjectInspector, responsible for one
property
known issues:
- rebuildPropertyUI can cause problems now: If the user clicks into
the control for property A, which causes property B to be committed,
which causes the UI for property A to be rebuilt, then this will
crash currently. Reason: rebuildPropertyUI now synchronously replaces
the VCL-Window of the rebuilt control, which is exactly the one
which is still in some MouseButtonDown-handler.
possible solutions:
- see if rebuiltPropertyUI can be obsoleted - handlers should be able
to just obtain the XPropertyControl from the PropertyUI, and
re-initialize the control. Shouldn't they?`
- make one of the steps in the chain (mouse-click, handler-call,
rebuildPropertyUI-callback) asynchronous.
2005/08/31 08:28:54 fs 1.6.156.4: #i53095# get rid of Set/GetPropertyName at the IBrowserControl
2005/08/12 16:30:07 fs 1.6.156.3: - more fine-grained control in the IPropertyBrowserUI which elements
to enable or disable
- moved designing the SQL command into a dedicated handler
- some more reactions on actuating properties move to dedicated handlers
- *nearly* completed implementation of the "composed browser UI", which
collects and combines UI change requests (IPropertyBrowserUI)
(still missing: proper auto-firing)
2005/08/10 15:41:42 fs 1.6.156.2: #i53095#
get rid of nearly all [1] the implementations in OPropertyBrowserController::Clicked,
and move them to a FormComponentHandler
[1] still to migrate:
- browsing for events (needs a dedicated event property handler)
- handling for clicking the button of the Command property - this
is kind of asynchronous, and IPropertyHandler is not yet prepared for this
2005/08/09 13:59:54 fs 1.6.156.1: #i53095# phase 1:
- don't use strings to transver values between controls and introspectee, but Anys
- first version of a dedicated property handler for form-component-related properties
(not yet completed)
known regressions over previous phase:
- handlers for events not yet implemented, thus some assertions
- click handlers for form-component-related properties do not yet work,
thus the browse buttons mostly do not work
2006-03-14 10:17:37 +00:00
|
|
|
|
|
|
|
/** retrieves the ->BrowserLinePointer for a given entry name
|
|
|
|
@param _rEntryName
|
|
|
|
the name whose line is to be looked up
|
|
|
|
@param _out_rpLine
|
|
|
|
contains, upon return, the found browser line, if any
|
|
|
|
@return
|
|
|
|
<TRUE/> if and only if a non-<NULL/> line for the given entry name could be
|
|
|
|
found.
|
|
|
|
*/
|
2013-04-07 12:06:47 +02:00
|
|
|
bool impl_getBrowserLineForName( const OUString& _rEntryName, BrowserLinePointer& _out_rpLine ) const;
|
2006-07-26 06:52:48 +00:00
|
|
|
|
2006-12-13 10:55:49 +00:00
|
|
|
/** returns the preferred height (in pixels) of the help section, or 0 if we
|
|
|
|
currently don't have a help section
|
|
|
|
*/
|
|
|
|
long impl_getPrefererredHelpHeight();
|
|
|
|
|
2006-07-26 06:52:48 +00:00
|
|
|
private:
|
|
|
|
using Window::Activate;
|
2001-01-12 10:35:45 +00:00
|
|
|
};
|
|
|
|
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
} // namespace pcr
|
2014-02-25 18:36:00 +01:00
|
|
|
|
2001-01-12 10:35:45 +00:00
|
|
|
|
2014-04-18 20:41:29 +02:00
|
|
|
#endif // INCLUDED_EXTENSIONS_SOURCE_PROPCTRLR_BROWSERLISTBOX_HXX
|
2001-01-12 10:35:45 +00:00
|
|
|
|
|
|
|
|
2010-10-27 12:45:03 +01:00
|
|
|
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
|