Lines Matching refs:p
60 <p>The <type>ObjectInspector</type> itself does not know anything about the object
64 component.</p>
75 …<p><member scope="com::sun::star::lang">XComponent::dispose</member> is invoked when the property …
77 resources here.</p>
148 … <p>In <member>describePropertyLine</member>, a property handler declared which type of control
151 conversions between controls values and property values are needed.</p>
153 … <p>This method converts a control value into a property value, which subsequently can be used
154 in conjunction with <member>setPropertyValue</member>.</p>
179 … <p>In <member>describePropertyLine</member>, a property handler declared which type of control
182 conversions between controls values and property values are needed.</p>
184 <p>This method converts a property value, which has previously been obtained using
186 with <type>XPropertyControl</type>'s <member>XPropertyControl::Value</member> attribute.</p>
188 … <p>A usual application of this method are list boxes: There is a generic list box implementation,
191 … <member>convertToControlValue</member> and <member>convertToPropertyValue</member> are used.</p>
193 …<p>The method is not invoked if the control's value type (<member>XPropertyControl::ValueType</mem…
194 equals the property's value type.</p>
226 <p>An <type>XPropertyHandler</type> implementation might decide to ignore this call.
228 reflected in the object inspector.</p>
230 <p>If a handler implementation supports property change listeners, it must be able to cope
233 is set in the next <member>inspect</member> call.</p>
253 <p>A handler is allowed to return an empty sequence here, indicating that for
256 where not all handlers can really cope with all components.</p>
258 <p>In the case of returning an empty sequence here, the property handler is ignored
259 by all further processing in the object inspector.</p>
266 <p>Besides defining an own set of properties (see <member>getSupportedProperties</member>),
268 <em>not</em> responsible for) are superseded by its own properties.</p>
270 <p>This is usually used if your handler is used with another, more generic one, which
272 handler handles more elegantly.</p>
274 <p>In such a case, simply return those properties here.</p>
276 <p>There is a precedence in the property handlers used by an <type>ObjectInspector</type>,
279 <member>XObjectInspectorModel::HandlerFactories</member> attribute.</p>
281 <p>With this in mind, property handlers can only supersede properties which are supported
282 by a handler preceding them, but not properties of handlers succeeding them.</p>
284 <p>For instance, imaging an <type>XObjectInspectorModel</type> which provides three
290 <code>C</code>.</p>
292 <p>If <member>getSupportedProperties</member> returned an empty sequence, this method will
293 not be called.</p>
302 <p>In general, properties can be declared as "actuating", that is, when their value
303 changes, the UI for other properties needs to be updated (e.g. enabled or disabled).</p>
305 <p>With this method, a handler can declare that it feels responsible for some/all
306 of the depending properties of certain actuating properties.</p>
308 <p>Whenever the value of an actuating property changes, all handlers which expressed
310 <member>actuatingPropertyChanged</member> method.</p>
312 <p>If <member>getSupportedProperties</member> returned an empty sequence, this method will
313 not be called</p>
320 …<p>An object inspector can inspect multiple components at once, displaying the <em>intersection</e…
323 are displayed in the inspector UI.</p>
335 … <p>Property handlers can raise a dedicated UI for entering or somehow changing a property value.
336 … Usually, this will be a modal dialog, but it can also be a non-modal user interface component.</p>
338 …<p>Availability of this feature is indicated by the <member>LineDescriptor::HasPrimaryButton</memb…
340 …ch the <type>XPropertyHandler</type> fills in its <member>describePropertyLine</member> method.</p>
342 <p>When this method is called, the property handler should raise the UI needed to enter the
343 … property value, and return the result of this (see <type>InteractiveSelectionResult</type>).</p>
345 <p>It is recommended that property handlers do not directly set the property value which has
347 <member>InteractiveSelectionResult::ObtainedValue</member>.</p>
349 <p>If a handler sets the new property value directly, and returns
354 all handlers.</p>
356 …<p>If a property is not composeable, directly setting the new property value does not yield any pr…
357 as long as property listeners are properly notified of the change.</p>
399 <p>This method is called whenever a property value changes, limited to those properties
400 … whose changes the handler expressed interest in (see <member>getActuatingProperties</member>).</p>
435 <p>A <type>XPropertyHandler</type> is used by a <type>XObjectInspector</type> instance,
438 all it's handlers.</p>
440 <p>The usual use case for this method are non-modal user interface components used
444 component, and veto suspension of the <type>XObjectInspector</type> as appropriate.</p>
446 <p>If suspension is not to be vetoed, then all non-modal UI components opened
447 … by the handler should have been closed when it returns from the <member>suspend</member> call.</p>