diff options
| author | Michael Stahl <mstahl@redhat.com> | 2013-04-27 22:45:02 +0200 |
|---|---|---|
| committer | Michael Stahl <mstahl@redhat.com> | 2013-06-04 12:01:01 +0200 |
| commit | ea71a05840f53158f669182c6e93de9f8348bbe5 (patch) | |
| tree | 4b2ee9dbaf603e319f995cbf4ee6223a82ad8e71 /offapi/com | |
| parent | 3122600a5e11309b86e33061defd710cf0872975 (diff) | |
*api: convert <member scope="foo">bar</member>
sed -i 's,<member scope="\([^"]*\)">\([^<]*::[a-z][^<:]\+[^)]\)</member>,\1::\2(),g'
Change-Id: I265ff28fee73a271f205294e59955b3a1c81d95a
Diffstat (limited to 'offapi/com')
70 files changed, 147 insertions, 147 deletions
diff --git a/offapi/com/sun/star/awt/XPrinter.idl b/offapi/com/sun/star/awt/XPrinter.idl index 0619c5ea7805..12af1976c8d0 100644 --- a/offapi/com/sun/star/awt/XPrinter.idl +++ b/offapi/com/sun/star/awt/XPrinter.idl @@ -36,8 +36,8 @@ <p>All properties are vetoable properties. If you change the properties between a call to - <member scope="com::sun::star::awt">XPrinter::startPage</member> and a call - to <member scope="com::sun::star::awt">XPrinter::endPage</member>, + com::sun::star::awt::XPrinter::startPage() and a call + to com::sun::star::awt::XPrinter::endPage(), a com::sun::star::beans::PropertyVetoException is thrown.</p> */ @@ -68,12 +68,12 @@ published interface XPrinter: com::sun::star::awt::XPrinterPropertySet /** stops the current print job. <p>If the method - <member scope="com::sun::star::awt">XPrinter::end</member> + com::sun::star::awt::XPrinter::end() is called beforehand, then this call does nothing. If you call - <member scope="com::sun::star::awt">XPrinter::terminate</member> + com::sun::star::awt::XPrinter::terminate() in or before the call to - <member scope="com::sun::star::awt">XPrinter::start</member>, - <member scope="com::sun::star::awt">XPrinter::terminate</member> + com::sun::star::awt::XPrinter::start(), + com::sun::star::awt::XPrinter::terminate() returns <FALSE/>. This call must not block the thread.</p> @see end diff --git a/offapi/com/sun/star/awt/XPrinterPropertySet.idl b/offapi/com/sun/star/awt/XPrinterPropertySet.idl index 18ef31667bd6..9d5c4fd6f033 100644 --- a/offapi/com/sun/star/awt/XPrinterPropertySet.idl +++ b/offapi/com/sun/star/awt/XPrinterPropertySet.idl @@ -33,8 +33,8 @@ /** represents an extended property set for printer properties. <p>All properties are vetoable properties. If you change the properties - between <member scope="com::sun::star::awt">XPrinter::startPage</member> - and <member scope="com::sun::star::awt">XPrinter::endPage</member>, a + between com::sun::star::awt::XPrinter::startPage() + and com::sun::star::awt::XPrinter::endPage(), a com::sun::star::beans::PropertyVetoException is thrown.</p> diff --git a/offapi/com/sun/star/awt/XPrinterServer.idl b/offapi/com/sun/star/awt/XPrinterServer.idl index 3c4070d0a273..f72470b8cfbc 100644 --- a/offapi/com/sun/star/awt/XPrinterServer.idl +++ b/offapi/com/sun/star/awt/XPrinterServer.idl @@ -43,7 +43,7 @@ published interface XPrinterServer: com::sun::star::uno::XInterface /** creates a new virtual printer. <p>You must call - <member scope="com::sun::star::awt">XPrinter::start</member> + com::sun::star::awt::XPrinter::start() to put the job into the printer spooler.</p> */ com::sun::star::awt::XPrinter createPrinter( [in] string printerName ); diff --git a/offapi/com/sun/star/awt/grid/XGridColumnModel.idl b/offapi/com/sun/star/awt/grid/XGridColumnModel.idl index 6ef4c5923253..35a24eb5d693 100644 --- a/offapi/com/sun/star/awt/grid/XGridColumnModel.idl +++ b/offapi/com/sun/star/awt/grid/XGridColumnModel.idl @@ -117,8 +117,8 @@ published interface XGridColumnModel /** Fills the model with the given number of default columns <p>Existing columns will be removed before adding new columns. Listeners at the column model will - be notified one <member scope="com::sun::star::container">XContainerListener::elementRemoved</member> event - for each removed column, and one <member scope="com::sun::star::container">XContainerListener::elementInserted</member> + be notified one com::sun::star::container::XContainerListener::elementRemoved() event + for each removed column, and one com::sun::star::container::XContainerListener::elementInserted() event for each insertion.</p> @param elements diff --git a/offapi/com/sun/star/chart/AccessibleChartDocumentView.idl b/offapi/com/sun/star/chart/AccessibleChartDocumentView.idl index 63bf4af7c445..1d4f8621df1b 100644 --- a/offapi/com/sun/star/chart/AccessibleChartDocumentView.idl +++ b/offapi/com/sun/star/chart/AccessibleChartDocumentView.idl @@ -77,7 +77,7 @@ service AccessibleChartDocumentView ways.</dd> <dt>Relations</dt> <dd>At the moment relations are not supported. The method - <member scope="com::sun::star::accessibility">XAccessibleContext::getAccessibleRelationSet</member> + com::sun::star::accessibility::XAccessibleContext::getAccessibleRelationSet() will always return an empty set.</dd> <dt>States</dt> <dd>The following states are supported: diff --git a/offapi/com/sun/star/chart2/PropertyPool.idl b/offapi/com/sun/star/chart2/PropertyPool.idl index 5a2303818bc5..42ac558bd8d6 100644 --- a/offapi/com/sun/star/chart2/PropertyPool.idl +++ b/offapi/com/sun/star/chart2/PropertyPool.idl @@ -45,7 +45,7 @@ service PropertyPool implementation of com::sun::star::beans::XPropertySet, the method - <member scope="com::sun::star::style">XDefaultsSupplier::getDefaults</member> + com::sun::star::style::XDefaultsSupplier::getDefaults() should return itself. */ interface ::com::sun::star::style::XDefaultsSupplier; diff --git a/offapi/com/sun/star/chart2/XChartDocument.idl b/offapi/com/sun/star/chart2/XChartDocument.idl index 82a9ddff1a8d..e57ec010eb45 100644 --- a/offapi/com/sun/star/chart2/XChartDocument.idl +++ b/offapi/com/sun/star/chart2/XChartDocument.idl @@ -85,7 +85,7 @@ interface XChartDocument : ::com::sun::star::frame::XModel createInternalDataProvider() has been called, but this is not necessary. The chart can also create an internal data provider by other means, e.g. a call to - <member scope="com::sun::star::frame">XModel::initNew</member>. + com::sun::star::frame::XModel::initNew(). </p> */ boolean hasInternalDataProvider(); diff --git a/offapi/com/sun/star/deployment/XPackageTypeInfo.idl b/offapi/com/sun/star/deployment/XPackageTypeInfo.idl index ce4e4d8f8dc8..2e347545b856 100644 --- a/offapi/com/sun/star/deployment/XPackageTypeInfo.idl +++ b/offapi/com/sun/star/deployment/XPackageTypeInfo.idl @@ -59,7 +59,7 @@ interface XPackageTypeInfo /** returns a file filter string for the file picker user interface. Both, the short description string and file filter string will be passed to - <member scope="com::sun::star::ui::dialogs">XFilterManager::appendFilter</member>. + com::sun::star::ui::dialogs::XFilterManager::appendFilter(). @return file filter string diff --git a/offapi/com/sun/star/document/MediaDescriptor.idl b/offapi/com/sun/star/document/MediaDescriptor.idl index 0d8c3aae6365..bdbab9980c6a 100644 --- a/offapi/com/sun/star/document/MediaDescriptor.idl +++ b/offapi/com/sun/star/document/MediaDescriptor.idl @@ -536,7 +536,7 @@ service MediaDescriptor <p>If this property is used when loading a document into a frame, then it specifies the name of the view controller to create. That is, the property - is passed to the document's <member scope="com::sun::star::frame">XModel2::createViewController</member> + is passed to the document's com::sun::star::frame::XModel2::createViewController() method.<br/> If the loaded document does not support the <code>XModel2</code> interface, the property is ignored.</p> diff --git a/offapi/com/sun/star/document/XDocumentRecovery.idl b/offapi/com/sun/star/document/XDocumentRecovery.idl index 6b9954882064..3507a43b804d 100644 --- a/offapi/com/sun/star/document/XDocumentRecovery.idl +++ b/offapi/com/sun/star/document/XDocumentRecovery.idl @@ -44,7 +44,7 @@ interface XDocumentRecovery <p>It's allowed to implement this method sloppy, by returning <TRUE/> in cases where it is not sure whether the document actually has been modified. So, the most simple implementation could simply delegate this call - to <member scope="com::sun::star::util">XModifiable::isModified</member>. (Well, actually that's the + to com::sun::star::util::XModifiable::isModified(). (Well, actually that's the second simple implementation, the <em>most</em> simple one would, still legitimately, always return <TRUE/>.)</p> <p>However, in such a case, the document might be saved more often than needed. In particular during the @@ -56,7 +56,7 @@ interface XDocumentRecovery /** does an emergency save of the document <p>A default implementation of this method could simply delegate this call to - <member scope="com::sun::star::frame">XStorable::storeToURL</member>.</p> + com::sun::star::frame::XStorable::storeToURL().</p> @param TargetLocation specifies the URL of the location to which the document should be emergency-saved. @@ -77,16 +77,16 @@ interface XDocumentRecovery /** recovers the document after a previous emergency or session save. <p>The document itself has previously been created, but <em>not</em> loaded - (via <member scope="com::sun::star::frame">XLoadable::load</member>) or initialized (via - <member scope="com::sun::star::frame">XLoadable::initNew</member>).</p> + (via com::sun::star::frame::XLoadable::load()) or initialized (via + com::sun::star::frame::XLoadable::initNew()).</p> <p>Upon successful return, the document must be fully initialized. In particular, the - caller is not responsible for calling <member scope="com::sun::star::frame">XModel::attachResource</member>. + caller is not responsible for calling com::sun::star::frame::XModel::attachResource(). Instead, the implementation is responsible to do so, if required.</p> <p>A default implementation of this method could simply delegate this call to - <member scope="::com::sun::star::frame:">XLodable::load</member>, followed by - <member scope="com::sun::star::frame">XModel::attachResource</member>.</p> + ::com::sun::star::frame:::XLodable::load(), followed by + com::sun::star::frame::XModel::attachResource().</p> @param SourceLocation specifies the URL of the location to which the document was previously emergency-saved. diff --git a/offapi/com/sun/star/document/XScriptInvocationContext.idl b/offapi/com/sun/star/document/XScriptInvocationContext.idl index e950c9b614f1..9ccd9b96bd3c 100644 --- a/offapi/com/sun/star/document/XScriptInvocationContext.idl +++ b/offapi/com/sun/star/document/XScriptInvocationContext.idl @@ -40,7 +40,7 @@ module com { module sun { module star { module document { <p>If the interface is implemented by a controller, then <member>ScriptContainer</member> refers to the document which supports embedding scripts, and which is unambiguously associated with the controller. This must not necessarily be the model returned by - <member scope="com::sun::star::frame">XController::getModel</member>.</p> + com::sun::star::frame::XController::getModel().</p> @since OOo 2.4 */ diff --git a/offapi/com/sun/star/document/XUndoManager.idl b/offapi/com/sun/star/document/XUndoManager.idl index b6c418cf2f36..c476d302bc6a 100644 --- a/offapi/com/sun/star/document/XUndoManager.idl +++ b/offapi/com/sun/star/document/XUndoManager.idl @@ -75,7 +75,7 @@ interface XUndoManager /** allows accessing the component, usually a document, which the undo manager works for. - <p><member scope="com::sun::star::container">XChild::setParent</member> is not supported, and will throw + <p>com::sun::star::container::XChild::setParent() is not supported, and will throw an com::sun::star::lang::NoSupportException.</p> */ interface ::com::sun::star::container::XChild; diff --git a/offapi/com/sun/star/embed/FileSystemStorageFactory.idl b/offapi/com/sun/star/embed/FileSystemStorageFactory.idl index 0ee7c960f45e..c51da0b48d74 100644 --- a/offapi/com/sun/star/embed/FileSystemStorageFactory.idl +++ b/offapi/com/sun/star/embed/FileSystemStorageFactory.idl @@ -71,7 +71,7 @@ The parameters are optional, that means that sequence can be empty or contain only first parameter, or first and second one. In case no parameters are provided the call works the same way as - <member scope="com::sun::star::lang">XSingleServiceFactory::createInstance</member>. + com::sun::star::lang::XSingleServiceFactory::createInstance(). In case only first parameter is provided, the storage is opened in readonly mode. </p> diff --git a/offapi/com/sun/star/embed/StorageFactory.idl b/offapi/com/sun/star/embed/StorageFactory.idl index 800ac9fbaccd..aa3687f6bdcf 100644 --- a/offapi/com/sun/star/embed/StorageFactory.idl +++ b/offapi/com/sun/star/embed/StorageFactory.idl @@ -88,7 +88,7 @@ The parameters are optional, that means that sequence can be empty or contain only first parameter, or first and second one. In case no parameters are provided the call works the same way as - <member scope="com::sun::star::lang">XSingleServiceFactory::createInstance</member>. + com::sun::star::lang::XSingleServiceFactory::createInstance(). In case only first parameter is provided, the storage is opened in readonly mode. </p> diff --git a/offapi/com/sun/star/form/FormComponent.idl b/offapi/com/sun/star/form/FormComponent.idl index d81cdc554b51..51afe410bf7a 100644 --- a/offapi/com/sun/star/form/FormComponent.idl +++ b/offapi/com/sun/star/form/FormComponent.idl @@ -80,7 +80,7 @@ published service FormComponent <p>Note that dynamic properties added to a form component are, by definition, removable. That is, the <member scope="com::sun::star::beans">PropertyAttribute::REMOVABLE</member> will always be set, even if you do not specify it in the - <member scope="com::sun::star::beans">XPropertyContainer::addProperty</member> call.</p> + com::sun::star::beans::XPropertyContainer::addProperty() call.</p> @since OOo 2.3 */ diff --git a/offapi/com/sun/star/form/FormComponents.idl b/offapi/com/sun/star/form/FormComponents.idl index 5e0f8188a924..577cab2b5e55 100644 --- a/offapi/com/sun/star/form/FormComponents.idl +++ b/offapi/com/sun/star/form/FormComponents.idl @@ -68,7 +68,7 @@ published service FormComponents <p>For instance, at any time you can obtain the events associated with the <code>n</code><super>th</super> element in the form components by calling - <member scope="com::sun::star::script">XEventAttacherManager::getScriptEvents</member> + com::sun::star::script::XEventAttacherManager::getScriptEvents() with parameter <code>n</code>. In particular, this invariant is always met, even after you inserted/removed elements into/from the container.</p> */ diff --git a/offapi/com/sun/star/form/XDatabaseParameterBroadcaster2.idl b/offapi/com/sun/star/form/XDatabaseParameterBroadcaster2.idl index 83af94682c52..660dd03cb1ba 100644 --- a/offapi/com/sun/star/form/XDatabaseParameterBroadcaster2.idl +++ b/offapi/com/sun/star/form/XDatabaseParameterBroadcaster2.idl @@ -29,7 +29,7 @@ module com { module sun { module star { module form { <p>Note that this interface provides exactly the same functionality as the XDatabaseParameterBroadcaster interface. It exists purely for compatibility - with the <member scope="com::sun::star::script">XEventAttacher::attachSingleEventListener</member>: + with the com::sun::star::script::XEventAttacher::attachSingleEventListener(): It expects the methods for adding and removing listeners to follow a certain naming scheme, respective to the name of the listener which is being added/removed.</p> diff --git a/offapi/com/sun/star/form/XForms.idl b/offapi/com/sun/star/form/XForms.idl index 14f8c52aef88..44f63a74f0c4 100644 --- a/offapi/com/sun/star/form/XForms.idl +++ b/offapi/com/sun/star/form/XForms.idl @@ -65,7 +65,7 @@ published interface XForms <p>For instance, at any time you can obtain the events associated with the <code>n</code><super>th</super> element in the form components by calling - <member scope="com::sun::star::script">XEventAttacherManager::getScriptEvents</member> + com::sun::star::script::XEventAttacherManager::getScriptEvents() with parameter <code>n</code>. In particular, this invariant is always met, even after you inserted/removed elements into/from the container.</p> */ diff --git a/offapi/com/sun/star/form/binding/BindableDataAwareControlModel.idl b/offapi/com/sun/star/form/binding/BindableDataAwareControlModel.idl index f145990f06c1..37816360a038 100644 --- a/offapi/com/sun/star/form/binding/BindableDataAwareControlModel.idl +++ b/offapi/com/sun/star/form/binding/BindableDataAwareControlModel.idl @@ -46,7 +46,7 @@ module com { module sun { module star { module form { module binding { it's column in this particular row.<br/> On the other hand, when any change in the control model (e.g. resulting from a user entering data in a control associated with the control model) is committed - (<member scope="com::sun::star::form">XBoundComponent::commit</member>), then the actual + (com::sun::star::form::XBoundComponent::commit()), then the actual data of the control model is written into the associated com::sun::star::form::component::DataForm column.</p> @@ -76,7 +76,7 @@ module com { module sun { module star { module form { module binding { in the external binding. This is a difference to SQL bindings of most com::sun::star::form::DataAwareControlModel's, where changes in the control model's value are only propagated to the bound column upon explicit - request via <member scope="com::sun::star::form">XBoundComponent::commit</member>.<br/> + request via com::sun::star::form::XBoundComponent::commit().<br/> Note that this restriction is inherited from the BindableControlModel. </li> <li><b>Cloning</b><br/> diff --git a/offapi/com/sun/star/form/binding/BindableDatabaseComboBox.idl b/offapi/com/sun/star/form/binding/BindableDatabaseComboBox.idl index b63d271e1260..4f57f9e02836 100644 --- a/offapi/com/sun/star/form/binding/BindableDatabaseComboBox.idl +++ b/offapi/com/sun/star/form/binding/BindableDatabaseComboBox.idl @@ -34,7 +34,7 @@ module com { module sun { module star { module form { module binding { <p>If an com::sun::star::form::binding::ValueBinding instance is set at the field, it will exchange it's text with the binding as <em>string</em>, thus only bindings supporting string exchange will be accepted in - <member scope="com::sun::star::form::binding">XValueBinding::setValueBinding</member>. + com::sun::star::form::binding::XValueBinding::setValueBinding(). </p> @see com::sun::star::form::binding::XValueBinding::supportsType diff --git a/offapi/com/sun/star/form/binding/BindableDatabaseTextField.idl b/offapi/com/sun/star/form/binding/BindableDatabaseTextField.idl index 7cf7135ce574..b894c0f73f91 100644 --- a/offapi/com/sun/star/form/binding/BindableDatabaseTextField.idl +++ b/offapi/com/sun/star/form/binding/BindableDatabaseTextField.idl @@ -33,7 +33,7 @@ module com { module sun { module star { module form { module binding { <p>If an com::sun::star::form::binding::ValueBinding instance is set at the field, it will exchange it's text with the binding as <em>string</em>, thus only bindings supporting string exchange will be accepted in - <member scope="com::sun::star::form::binding">XValueBinding::setValueBinding</member>. + com::sun::star::form::binding::XValueBinding::setValueBinding(). </p> @see com::sun::star::form::binding::XValueBinding::supportsType diff --git a/offapi/com/sun/star/form/component/CommandButton.idl b/offapi/com/sun/star/form/component/CommandButton.idl index d5eeb7441acb..32cd607826cf 100644 --- a/offapi/com/sun/star/form/component/CommandButton.idl +++ b/offapi/com/sun/star/form/component/CommandButton.idl @@ -90,7 +90,7 @@ published service CommandButton <p>This property is meaningful only when <member scope="com::sun::star::awt">UnoControlButtonModel::Toggle</member> is <TRUE/>. In this case, the <code>DefaultState</code> controls to which <code>State</code> the button will - be reset, when <member scope="com::sun::star::form">XReset::reset</member> is invoked.</p> + be reset, when com::sun::star::form::XReset::reset() is invoked.</p> <p>For a given implementation of the interface, if this (optional) interface is present, then also the optional property <member>DefaultState</member> must be present.</p> diff --git a/offapi/com/sun/star/form/component/DataForm.idl b/offapi/com/sun/star/form/component/DataForm.idl index 4c982347d443..6700105e49ae 100644 --- a/offapi/com/sun/star/form/component/DataForm.idl +++ b/offapi/com/sun/star/form/component/DataForm.idl @@ -55,9 +55,9 @@ published service DataForm to the insertion row.</p> <p>The insertion row is a virtual row which is used to insert new records. It is reached - by calling <member scope="com::sun::star::sdbc">XResultSetUpdate::moveToInsertRow</member>. + by calling com::sun::star::sdbc::XResultSetUpdate::moveToInsertRow(). The com::sun::star::sdb::RowSet service specifies exactly which notifications - happen in which order when calling <member scope="com::sun::star::sdbc">XResultSetUpdate::moveToInsertRow</member>, + happen in which order when calling com::sun::star::sdbc::XResultSetUpdate::moveToInsertRow(), and a DataForm implementation extends this with the following contract: <ul><li>After all notifications as defined in the com::sun::star::sdb::RowSet service have been sent, the DataForm resets itself, if all @@ -65,7 +65,7 @@ published service DataForm <li>After the reset happened, the <member scope="com::sun::star::sdb">RowSet::IsModified</member> property is reset to <FALSE/>. This property might have been switched to <TRUE/> during listener notifications, since listeners are allowed to change field values. Also, the - <member scope="com::sun::star::form">XReset::reset</member> implementations of bound control + com::sun::star::form::XReset::reset() implementations of bound control models might have modified the fields they're bound to (by filling them with default values).</li> <li>The reset listeners are notified of the completed reset operation.</li> </ul></p> @@ -75,9 +75,9 @@ published service DataForm /** used to load/unload the form <p>Loading a form is basically the same as executing the underlying row set. In fact, all the functionality of this interface could be simulated by using setting some properties manually, - <member scope="com::sun::star::sdbc">XRowSet::execute</member>, moving the row set cursor and so on.</p> + com::sun::star::sdbc::XRowSet::execute(), moving the row set cursor and so on.</p> - <p>One main difference between XLoadable::load() and <member scope="com::sun::star::sdbc">XRowSet::execute</member> + <p>One main difference between XLoadable::load() and com::sun::star::sdbc::XRowSet::execute() is that if you use the former, the row set is positioned on the first record, while in the latter case it is position <em>before</em> the it.</p> */ @@ -104,7 +104,7 @@ published service DataForm fill them by their own choice.</p> <p>This is slightly changed if the form is loaded using the - <member scope="com::sun::star::sdb">XCompletedExecution::connectWithCompletion</member> method. In this case, the parameters + com::sun::star::sdb::XCompletedExecution::connectWithCompletion() method. In this case, the parameters are obtained from the interaction handler, not from the listeners</p> @see XCompletedExecution diff --git a/offapi/com/sun/star/form/component/DatabaseImageControl.idl b/offapi/com/sun/star/form/component/DatabaseImageControl.idl index 02984b1f6eef..507c229616ae 100644 --- a/offapi/com/sun/star/form/component/DatabaseImageControl.idl +++ b/offapi/com/sun/star/form/component/DatabaseImageControl.idl @@ -36,7 +36,7 @@ can be bound to a database field. This means that for instance with every record change, the content of the database field is taken, interpreted as image, and displayed in the control.<br/> Unlike other more text-based controls, it does not interpret the content of the field as text or double, - but as binary stream (see <member scope="com::sun::star::sdb">XColumn::getBinaryStream</member>).</p> + but as binary stream (see com::sun::star::sdb::XColumn::getBinaryStream()).</p> <p>Usually, an image control model can be bound to binary columns only, namely <member scope="com::sun::star::sdbc">DataType::BINARY</member>, diff --git a/offapi/com/sun/star/form/component/GridControl.idl b/offapi/com/sun/star/form/component/GridControl.idl index 11bcb2e75e56..1370da91e51f 100644 --- a/offapi/com/sun/star/form/component/GridControl.idl +++ b/offapi/com/sun/star/form/component/GridControl.idl @@ -77,7 +77,7 @@ published service GridControl /** allows to create column models to be inserted into the control model. - <p>Note that the object returned by the <member scope="com::sun::star::form">XGridColumnFactory::createColumn</member> + <p>Note that the object returned by the com::sun::star::form::XGridColumnFactory::createColumn() method is not part of the grid control, yet. It needs to be inserted using any of the container interfaces.</p> diff --git a/offapi/com/sun/star/form/component/TextField.idl b/offapi/com/sun/star/form/component/TextField.idl index c297f799fd23..6308ba7a2667 100644 --- a/offapi/com/sun/star/form/component/TextField.idl +++ b/offapi/com/sun/star/form/component/TextField.idl @@ -42,7 +42,7 @@ published service TextField <p>If the <member>RichTextControl::RichText</member> property is set to <TRUE/>, then the TextField component will disable it's reset capabilities. This means - that all calls to <member scope="com::sun::star::form">XReset::reset</member> will be ignored.</p> + that all calls to com::sun::star::form::XReset::reset() will be ignored.</p> */ [optional] service RichTextControl; diff --git a/offapi/com/sun/star/form/control/SubmitButton.idl b/offapi/com/sun/star/form/control/SubmitButton.idl index 7f3c9a1f6bcf..d847166270f2 100644 --- a/offapi/com/sun/star/form/control/SubmitButton.idl +++ b/offapi/com/sun/star/form/control/SubmitButton.idl @@ -38,14 +38,14 @@ module com { module sun { module star { module form { module control { at the component are given the chance to veto the submission. </li> <li>The model of the control is examined for an external submission object. That is, - <member scope="com::sun::star::form::submission">XSubmissionSupplier::getSubmission</member> + com::sun::star::form::submission::XSubmissionSupplier::getSubmission() is called at the model.<br/> If there is such a submission object, its - <member scope="com::sun::star::form::submission">XSubmission::submit</member> method is invoked. + com::sun::star::form::submission::XSubmission::submit() method is invoked. </li> <li>If there is no external submission, the parent object of the model is examined for the presence of the com::sun::star::form::XSubmit interface. If it - is present, it's <member scope="com::sun::star::form">XSubmit::submit</member> method is + is present, it's com::sun::star::form::XSubmit::submit() method is invoked.<br/> Since the parent object of a submit button can only be a com::sun::star::form::component::Form, this means that SubmitButtons are also able to submit com::sun::star::form::component::HTMLForms. diff --git a/offapi/com/sun/star/form/runtime/FormFeature.idl b/offapi/com/sun/star/form/runtime/FormFeature.idl index a59573e1bc39..2405e00f3004 100644 --- a/offapi/com/sun/star/form/runtime/FormFeature.idl +++ b/offapi/com/sun/star/form/runtime/FormFeature.idl @@ -34,7 +34,7 @@ constants FormFeature /** moves the form to a record given by absolute position. <p>This operation cannot be executed without arguments. When executing it (i.e. - when calling <member scope="com::sun::star::form::runtime">XFormOperations::executeWithArguments</member>), + when calling com::sun::star::form::runtime::XFormOperations::executeWithArguments()), you need to specify a parameter named <em>Position</em> of type <code>long</code>, which denotes the position to move the form to.</p> */ diff --git a/offapi/com/sun/star/form/runtime/XFormController.idl b/offapi/com/sun/star/form/runtime/XFormController.idl index e38a473f1066..413cf01a3971 100644 --- a/offapi/com/sun/star/form/runtime/XFormController.idl +++ b/offapi/com/sun/star/form/runtime/XFormController.idl @@ -85,7 +85,7 @@ interface XFormControllerContext; a per-form and a per-database basis.<br/> For the former, you need to add a boolean property <code>FormsCheckRequiredFields</code> to the form (aka the <code>FormController</code>'s model), using its - <member scope="com::sun::star::beans">XPropertyContainer::addProperty</member> method, with a value + com::sun::star::beans::XPropertyContainer::addProperty() method, with a value of <FALSE/>.<br/> For the latter, you need to set the respective property of the data source's <code>Settings</code> (also named <code>FormsCheckRequiredFields</code>) to <FALSE/>.</p> @@ -107,7 +107,7 @@ interface XFormControllerContext; requesting a dispatcher for this functionality is <em>.uno:FormController/deleteRecord</em>.</p> <p>Some URLs may require parameters. For this, the sequence of com::sun::star::beans::PropertyValues - passed to the <member scope="com::sun::star::frame">XDispatch::dispatch</member> call is used - every property value is + passed to the com::sun::star::frame::XDispatch::dispatch() call is used - every property value is used as one named parameter.</p> <p>For all URLs, interested parties can register as status listeners (com::sun::star::frame::XStatusListener) @@ -245,7 +245,7 @@ interface XFormController { /** is used for tab controlling and grouping of the controls. - <p>The model obtained via <member scope="com::sun::star::awt">XTabController::getModel</member> is the form for which the + <p>The model obtained via com::sun::star::awt::XTabController::getModel() is the form for which the controller is responsible.</p> */ interface ::com::sun::star::awt::XTabController; diff --git a/offapi/com/sun/star/form/runtime/XFormOperations.idl b/offapi/com/sun/star/form/runtime/XFormOperations.idl index ac14fb4ceac6..fda9b9e8b5d9 100644 --- a/offapi/com/sun/star/form/runtime/XFormOperations.idl +++ b/offapi/com/sun/star/form/runtime/XFormOperations.idl @@ -42,11 +42,11 @@ interface XFeatureInvalidation; <p>As an example, imagine you have a database form, displayed in some user interface, which you want to move to the next record.<br/> - It is as easy as calling <member scope="com:::sun::star::sdbc">XResultSet::next</member> + It is as easy as calling com:::sun::star::sdbc::XResultSet::next() on this form, right? Wrong. First, you need to care for saving the current record, so the user doesn't lose her input. So you need to call - <member scope="com::sun::star::sdbc">XResultSetUpdate::updateRow</member> or - <member scope="com::sun::star::sdbc">XResultSetUpdate::insertRow</member>, depending + com::sun::star::sdbc::XResultSetUpdate::updateRow() or + com::sun::star::sdbc::XResultSetUpdate::insertRow(), depending on the form's <member scope="com::sun::star::sdb">RowSet::IsNew</member> property.<br/> But then you're done, right? Wrong, again.<br/> When the user just entered some data into one of the form fields, but did not yet diff --git a/offapi/com/sun/star/form/validation/ValidatableBindableControlModel.idl b/offapi/com/sun/star/form/validation/ValidatableBindableControlModel.idl index fb2bc5eae02d..319008cd5267 100644 --- a/offapi/com/sun/star/form/validation/ValidatableBindableControlModel.idl +++ b/offapi/com/sun/star/form/validation/ValidatableBindableControlModel.idl @@ -47,7 +47,7 @@ service ValidatableBindableControlModel /** specifies support for binding the control value to an external component <p>If a value binding is established at the control model (by using - <member scope="com::sun::star::form::binding">XBindableValue::setValueBinding</member> with a non-<NULL/> + com::sun::star::form::binding::XBindableValue::setValueBinding() with a non-<NULL/> binding), this binding is analyzed for validation support. If it is present (read: if the binding also supports the XValidator interface), the binding is also established as validator, as if it has been passed to XValidatable::setValidator().<br/> diff --git a/offapi/com/sun/star/frame/ToolbarController.idl b/offapi/com/sun/star/frame/ToolbarController.idl index 012c90a520e2..f41571c4219d 100644 --- a/offapi/com/sun/star/frame/ToolbarController.idl +++ b/offapi/com/sun/star/frame/ToolbarController.idl @@ -92,7 +92,7 @@ service ToolbarController <p> Mostly used by a toolbar implementation to forward information to and request services from a toolbar controller component. This interface must be usable - after <member scope="com::sun::star::lang">XInitialitation::initialize</member> + after com::sun::star::lang::XInitialitation::initialize() has been called. The behavior of the interface is undefined if the controller component hasn't been initialized. </p> diff --git a/offapi/com/sun/star/i18n/TransliterationModules.idl b/offapi/com/sun/star/i18n/TransliterationModules.idl index 7dfe9716dd99..2db2192c5c10 100644 --- a/offapi/com/sun/star/i18n/TransliterationModules.idl +++ b/offapi/com/sun/star/i18n/TransliterationModules.idl @@ -26,7 +26,7 @@ module com { module sun { module star { module i18n { /** Old transliteration module enumeration. <p> Use with <member>XTransliteration::loadModule()</member> and - <member scope="com::sun::star::util">SearchOptions::transliterateFlags</member> </p> + com::sun::star::util::SearchOptions::transliterateFlags() </p> <p> Note that values >=0x100 are logically or'ed with other values! </p> */ diff --git a/offapi/com/sun/star/inspection/XObjectInspector.idl b/offapi/com/sun/star/inspection/XObjectInspector.idl index c6cac35f3cd2..398bcccda11c 100644 --- a/offapi/com/sun/star/inspection/XObjectInspector.idl +++ b/offapi/com/sun/star/inspection/XObjectInspector.idl @@ -39,15 +39,15 @@ interface XObjectInspector { /** allows to plug the inspector into an com::sun::star::frame::XFrame - <p>The <member scope="com::sun::star::frame">XController::setModel</member> method + <p>The com::sun::star::frame::XController::setModel() method accepts only XObjectInspectorModels, and will return <FALSE/> if the to-be-attached model is not <NULL/>, but does not support this interface.</p> <p>If you do not want to support a full-blown com::sun::star::frame::XModel, use the <member>InspectorModel</member> attribute instead.</p> - <p>The <member scope="com::sun::star::frame">XController::getViewData</member> and - <member scope="com::sun::star::frame">XController::restoreViewData</member> exchange + <p>The com::sun::star::frame::XController::getViewData() and + com::sun::star::frame::XController::restoreViewData() exchange string values, which describes as much of the current view state as possible.</p> */ interface com::sun::star::frame::XController; @@ -65,7 +65,7 @@ interface XObjectInspector it can provide user interface names and help URLs for property categories.</p> <p>Note that there are two ways of setting or retrieving the current model: You can either - use <member scope="com::sun::star::frame">XModel::setModel</member>, or, if you do not want + use com::sun::star::frame::XModel::setModel(), or, if you do not want or need to implement the full-blown com::sun::star::frame::XModel interface, you can use this property directly. Both approaches are semantically equivalent.</p> diff --git a/offapi/com/sun/star/inspection/XPropertyHandler.idl b/offapi/com/sun/star/inspection/XPropertyHandler.idl index 9207f2a694a3..93fc7114d4a7 100644 --- a/offapi/com/sun/star/inspection/XPropertyHandler.idl +++ b/offapi/com/sun/star/inspection/XPropertyHandler.idl @@ -51,7 +51,7 @@ interface XPropertyHandler { /** used for controlling resources acquired by the handler - <p><member scope="com::sun::star::lang">XComponent::dispose</member> is invoked when the property handler is not + <p>com::sun::star::lang::XComponent::dispose() is invoked when the property handler is not needed by the object inspector anymore. Handler implementations should clean up any resources here.</p> */ @@ -391,7 +391,7 @@ interface XPropertyHandler If <TRUE/>, the method is called for the first-time update of the respective property, that is, when the property browser is just initializing with the properties of the introspected object.<br/> - If <FALSE/>, there was a real <member scope="com::sun::star::beans">XPropertyChangeListener::propertyChange</member> + If <FALSE/>, there was a real com::sun::star::beans::XPropertyChangeListener::propertyChange() event which triggered the call.<br/> <br/> In some cases it may be necessary to differentiate between both situations. For instance, @@ -414,7 +414,7 @@ interface XPropertyHandler <p>A XPropertyHandler is used by a XObjectInspector instance, which implements the XController interface. By definition, a XObjectInspector always forwards - all suspend requests (<member scope="com::sun::star::frame">XController::suspend</member>) to + all suspend requests (com::sun::star::frame::XController::suspend()) to all it's handlers.</p> <p>The usual use case for this method are non-modal user interface components used diff --git a/offapi/com/sun/star/linguistic2/DictionaryListEvent.idl b/offapi/com/sun/star/linguistic2/DictionaryListEvent.idl index 9254c2c9cffd..4ff7200b2a3a 100644 --- a/offapi/com/sun/star/linguistic2/DictionaryListEvent.idl +++ b/offapi/com/sun/star/linguistic2/DictionaryListEvent.idl @@ -63,7 +63,7 @@ published struct DictionaryListEvent : com::sun::star::lang::EventObject <p>It will be empty if all com::sun::star::linguistic2::XDictionaryListEventListener are satisfied with the condensed representation of the - <member scope="com::sun::star::linguistic2">DictionaryListEvent::nCondensedEvent</member>.</p> + com::sun::star::linguistic2::DictionaryListEvent::nCondensedEvent().</p> @see com::sun::star::linguistic2::DictionaryEvent */ diff --git a/offapi/com/sun/star/linguistic2/XDictionary.idl b/offapi/com/sun/star/linguistic2/XDictionary.idl index 5582a3720027..7d95abb84509 100644 --- a/offapi/com/sun/star/linguistic2/XDictionary.idl +++ b/offapi/com/sun/star/linguistic2/XDictionary.idl @@ -195,17 +195,17 @@ published interface XDictionary : com::sun::star::container::XNamed <P>On dictionary events, each entry in the listener list will be notified via a call to - <member scope="com::sun::star::linguistic2">XDictionaryEventListener::processDictionaryEvent</member>.</P> + com::sun::star::linguistic2::XDictionaryEventListener::processDictionaryEvent().</P> @param xListener the entry to be made, that is, the object that wants notifications. @returns <TRUE/> if the entry was successfully made, <FALSE/> otherwise. - If <member scope="com::sun::star::lang">XEventListener::disposing</member> was called before, + If com::sun::star::lang::XEventListener::disposing() was called before, it will always fail. - @see <member scope="com::sun::star::linguistic2">XDictionary::removeDictionaryEventListener</member> + @see com::sun::star::linguistic2::XDictionary::removeDictionaryEventListener() @see com::sun::star::linguistic2::XDictionaryEventListener */ boolean addDictionaryEventListener( @@ -220,7 +220,7 @@ published interface XDictionary : com::sun::star::container::XNamed <TRUE/> if the object to be removed was found and removed, <FALSE/> if the object was not found in the list. - @see <member scope="com::sun::star::linguistic2">XDictionary::addDictionaryEventListener</member> + @see com::sun::star::linguistic2::XDictionary::addDictionaryEventListener() @see com::sun::star::linguistic2::XDictionaryEventListener */ boolean removeDictionaryEventListener( diff --git a/offapi/com/sun/star/linguistic2/XDictionaryList.idl b/offapi/com/sun/star/linguistic2/XDictionaryList.idl index 50dbe3f999d2..6d0ff70f82a5 100644 --- a/offapi/com/sun/star/linguistic2/XDictionaryList.idl +++ b/offapi/com/sun/star/linguistic2/XDictionaryList.idl @@ -106,11 +106,11 @@ published interface XDictionaryList : com::sun::star::uno::XInterface <P>On dictionary-list events, each entry in the listener list will be notified via a call to - <member scope="com::sun::star::linguistic2">XDictionaryListEventListener::processDictionaryListEvent</member>.</P> + com::sun::star::linguistic2::XDictionaryListEventListener::processDictionaryListEvent().</P> @returns <TRUE/> if the entry was made, <FALSE/> otherwise. - If <member scope="com::sun::star::lang">XEventListener::disposing</member> + If com::sun::star::lang::XEventListener::disposing() was called before, it will always fail. @param xListener @@ -154,8 +154,8 @@ published interface XDictionaryList : com::sun::star::uno::XInterface @see com::sun::star::linguistic2::XDictionaryListEvent @see com::sun::star::linguistic2::XDictionaryListEventListener - @see <member scope="com::sun::star::linguistic2">XDictionaryList::endCollectEvents</member> - @see <member scope="com::sun::star::linguistic2">XDictionaryList::flushEvents</member> + @see com::sun::star::linguistic2::XDictionaryList::endCollectEvents() + @see com::sun::star::linguistic2::XDictionaryList::flushEvents() */ short beginCollectEvents(); @@ -172,8 +172,8 @@ published interface XDictionaryList : com::sun::star::uno::XInterface @see com::sun::star::linguistic2::XDictionaryListEvent @see com::sun::star::linguistic2::XDictionaryListEventListener - @see <member scope="com::sun::star::linguistic2">XDictionaryList::beginCollectEvents</member> - @see <member scope="com::sun::star::linguistic2">XDictionaryList::flushEvents</member> + @see com::sun::star::linguistic2::XDictionaryList::beginCollectEvents() + @see com::sun::star::linguistic2::XDictionaryList::flushEvents() */ short endCollectEvents(); @@ -185,8 +185,8 @@ published interface XDictionaryList : com::sun::star::uno::XInterface @see com::sun::star::linguistic2::XDictionaryListEvent @see com::sun::star::linguistic2::XDictionaryListEventListener - @see <member scope="com::sun::star::linguistic2">XDictionaryList::beginCollectEvents</member> - @see <member scope="com::sun::star::linguistic2">XDictionaryList::endCollectEvents</member> + @see com::sun::star::linguistic2::XDictionaryList::beginCollectEvents() + @see com::sun::star::linguistic2::XDictionaryList::endCollectEvents() */ short flushEvents(); diff --git a/offapi/com/sun/star/linguistic2/XMeaning.idl b/offapi/com/sun/star/linguistic2/XMeaning.idl index c93764d9afed..04fc8dc10750 100644 --- a/offapi/com/sun/star/linguistic2/XMeaning.idl +++ b/offapi/com/sun/star/linguistic2/XMeaning.idl @@ -28,7 +28,7 @@ module com { module sun { module star { module linguistic2 { /** one of the possible meanings for a word. <P> Represents one of the possible meanings that may be returned from a - <member scope="com::sun::star::linguistic2">XThesaurus::queryMeanings</member> + com::sun::star::linguistic2::XThesaurus::queryMeanings() call and allows for retrieval of its synonyms. </P> diff --git a/offapi/com/sun/star/linguistic2/XPossibleHyphens.idl b/offapi/com/sun/star/linguistic2/XPossibleHyphens.idl index 5e2bd1bc35bf..eb925f6ecb78 100644 --- a/offapi/com/sun/star/linguistic2/XPossibleHyphens.idl +++ b/offapi/com/sun/star/linguistic2/XPossibleHyphens.idl @@ -70,7 +70,7 @@ published interface XPossibleHyphens : com::sun::star::uno::XInterface within the original word which denotes a hyphenation position corresponding to one of the hyphens in the string returned by - <member scope="com::sun::star::linguistic2">XPossibleHyphens::getPossibleHyphens</member>. + com::sun::star::linguistic2::XPossibleHyphens::getPossibleHyphens(). */ sequence<short> getHyphenationPositions(); diff --git a/offapi/com/sun/star/linguistic2/XSpellAlternatives.idl b/offapi/com/sun/star/linguistic2/XSpellAlternatives.idl index b10fd00acc6b..8f5fd67fafb4 100644 --- a/offapi/com/sun/star/linguistic2/XSpellAlternatives.idl +++ b/offapi/com/sun/star/linguistic2/XSpellAlternatives.idl @@ -29,7 +29,7 @@ module com { module sun { module star { module linguistic2 { spell checking attempts and may provide spelling alternatives. <P>This is used by the - <member scope="com::sun::star::linguistic2">XSpellChecker::spell</member> + com::sun::star::linguistic2::XSpellChecker::spell() function when the word was not found to be correct. Suggestions for other words to be used may be provided along with a failure-type that may specify why the word was not correct. diff --git a/offapi/com/sun/star/rdf/XQuerySelectResult.idl b/offapi/com/sun/star/rdf/XQuerySelectResult.idl index 510f861e6aed..26ebc2d517b1 100644 --- a/offapi/com/sun/star/rdf/XQuerySelectResult.idl +++ b/offapi/com/sun/star/rdf/XQuerySelectResult.idl @@ -36,7 +36,7 @@ module com { module sun { module star { module rdf { each being a list of bindings for the above variables</li> </ol> Note that each query result retrieved via - <member scope="com::sun::star::container">XEnumeration::nextElement</member> + com::sun::star::container::XEnumeration::nextElement() has the type <type dim="[]">XNode</type>, the length of the sequence being the same as the number of query variables. </p> diff --git a/offapi/com/sun/star/resource/OfficeResourceLoader.idl b/offapi/com/sun/star/resource/OfficeResourceLoader.idl index abad49a85b18..becd687613c6 100644 --- a/offapi/com/sun/star/resource/OfficeResourceLoader.idl +++ b/offapi/com/sun/star/resource/OfficeResourceLoader.idl @@ -43,7 +43,7 @@ module com { module sun { module star { module resource { except that <code>Locale.getDefault()</code> is not used.</p> <p>Resource keys, as passed to the XResourceBundle::getDirectElement() or - <member scope="com::sun::star::container">XNameAccess::getByName</member>, have the following format: + com::sun::star::container::XNameAccess::getByName(), have the following format: <code><resource_type>:<numeric_identifier></code>, where <code><resource_type> specifies the type of the requested resource (see below) and <code><numeric_identifier></code> is the numeric identifier of the resource.</p> diff --git a/offapi/com/sun/star/sdb/DataAccessDescriptor.idl b/offapi/com/sun/star/sdb/DataAccessDescriptor.idl index 92a85c48e70b..3041fd90fa71 100644 --- a/offapi/com/sun/star/sdb/DataAccessDescriptor.idl +++ b/offapi/com/sun/star/sdb/DataAccessDescriptor.idl @@ -78,9 +78,9 @@ published service DataAccessDescriptor /** specifies additional info to use when creating a connection from a <code>ConnectionResource</code> <p>This member is evaluated only when <code>ConnectionResource</code> is used: In this case, - <member scope="com::sun::star::sdbc">XDriverManager::getConnectionWithInfo</member> is used + com::sun::star::sdbc::XDriverManager::getConnectionWithInfo() is used to create a connection for the given connection resource, instead of - <member scope="com::sun::star::sdbc">XDriverManager::getConnection</member>.</p> + com::sun::star::sdbc::XDriverManager::getConnection().</p> <p>If the sequence is empty, it is ignored.</p> */ @@ -185,7 +185,7 @@ published service DataAccessDescriptor <p>Note that any superservices of com::sun::star::sdbc::ResultSet are also allowed. Especially, this member can denote an instance of the com::sun::star::sdb::RowSet, or an instance obtained - by calling <member scope="com::sun::star::sdb">XResultSetAccess::createResultSet</member> + by calling com::sun::star::sdb::XResultSetAccess::createResultSet() on such a com::sun::star::sdb::RowSet. This becomes important in conjunction with the <member>Selection</member> property.</p> @@ -200,8 +200,8 @@ published service DataAccessDescriptor additionally refined with this property.</p> <p>The single elements of the <member>Selection</member> are either record numbers (see - <member scope="com::sun::star::sdbc">XResultSet::getRow</member>), or bookmarks (see - <member scope="com::sun::star::sdbcx">XRowLocate::getBookmark</member>).<br/> + com::sun::star::sdbc::XResultSet::getRow()), or bookmarks (see + com::sun::star::sdbcx::XRowLocate::getBookmark()).<br/> It is up to the component which provides or requires a DataAccessDescriptor to specify which of the two alternatives it expects. If it does <em>not</em> specify this, then the property <member>BookmarkSelection</member> becomes mandatory.</p> diff --git a/offapi/com/sun/star/sdb/DataSource.idl b/offapi/com/sun/star/sdb/DataSource.idl index 61d9742a899e..ba5bfd625995 100644 --- a/offapi/com/sun/star/sdb/DataSource.idl +++ b/offapi/com/sun/star/sdb/DataSource.idl @@ -151,7 +151,7 @@ published service DataSource <p>Additionally, the property bag supports default values of properties, and thus the com::sun::star::beans::XPropertyState interface. If you add an own property to - the bag using <member scope="com::sun::star::beans">XPropertyContainer::addProperty</member>, you need + the bag using com::sun::star::beans::XPropertyContainer::addProperty(), you need to specify an initial value, which is also used as default value (exceptions see below).</p> <p>Effectively, the property bag represented by <code>Settings</code> contains two classes of properties: diff --git a/offapi/com/sun/star/sdb/DataSourceBrowser.idl b/offapi/com/sun/star/sdb/DataSourceBrowser.idl index 541ae12a6fd9..d0dccd3ea78a 100644 --- a/offapi/com/sun/star/sdb/DataSourceBrowser.idl +++ b/offapi/com/sun/star/sdb/DataSourceBrowser.idl @@ -210,7 +210,7 @@ published service DataSourceBrowser <p> You may use the - <member scope="com::sun::star::frame">XDispatchProvider::queryDispatch</member> + com::sun::star::frame::XDispatchProvider::queryDispatch() method to query for objects which implement the com::sun::star::frame::XDispatch diff --git a/offapi/com/sun/star/sdb/DocumentContainer.idl b/offapi/com/sun/star/sdb/DocumentContainer.idl index 954ae0aac959..b8428777c8ac 100644 --- a/offapi/com/sun/star/sdb/DocumentContainer.idl +++ b/offapi/com/sun/star/sdb/DocumentContainer.idl @@ -49,7 +49,7 @@ usual com::sun::star::document::OfficeDocuments.<br/> The only thing worth mentioning here is that they support the com::sun::star::container::XChild interface, whose - <member scope="com::sun::star::container">XChild::getParent</member> method can be used to + com::sun::star::container::XChild::getParent() method can be used to obtain the database document which the embedded document belongs to. </p> @@ -63,7 +63,7 @@ service DocumentContainer /** provides functionality for treating the container as part of a hierarchy of a database document's sub documents. - <p>The <member scope="com::sun::star::ucb">XCommandProcessor::execute</member> method + <p>The com::sun::star::ucb::XCommandProcessor::execute() method of a <code>DocumentDefinition</code> supports at least the following commands, additionally to the ones already supported by the DefinitionContent: <ul> diff --git a/offapi/com/sun/star/sdb/DocumentDefinition.idl b/offapi/com/sun/star/sdb/DocumentDefinition.idl index b24bd8f30fda..4b19cac5ce7a 100644 --- a/offapi/com/sun/star/sdb/DocumentDefinition.idl +++ b/offapi/com/sun/star/sdb/DocumentDefinition.idl @@ -39,7 +39,7 @@ service DocumentDefinition /** provides functionality for treating the object as part of a hierarchy of a database document's sub documents. - <p>The <member scope="com::sun::star::ucb">XCommandProcessor::execute</member> method + <p>The com::sun::star::ucb::XCommandProcessor::execute() method of a <code>DocumentDefinition</code> supports at least the following commands, additionally to the ones already supported by the DefinitionContent: <ul> diff --git a/offapi/com/sun/star/sdb/OfficeDatabaseDocument.idl b/offapi/com/sun/star/sdb/OfficeDatabaseDocument.idl index f0c6a02f8b32..4a50efd4f02e 100644 --- a/offapi/com/sun/star/sdb/OfficeDatabaseDocument.idl +++ b/offapi/com/sun/star/sdb/OfficeDatabaseDocument.idl @@ -210,7 +210,7 @@ service OfficeDatabaseDocument life time issues, since a document needs to be closed when nobody needs it anymore.</p> <p>This implies that clients of a document need to ensure that as soon as they don't - need, they invoke <member scope="com::sun::star::util">XCloseable::close</member>.</p> + need, they invoke com::sun::star::util::XCloseable::close().</p> <p>Since this can be done by multiple clients, every client is additionally required to register itself as com::sun::star::util::XCloseListener at diff --git a/offapi/com/sun/star/sdb/RelationDesign.idl b/offapi/com/sun/star/sdb/RelationDesign.idl index 765c2fec4f3e..9d830c1c6b9f 100644 --- a/offapi/com/sun/star/sdb/RelationDesign.idl +++ b/offapi/com/sun/star/sdb/RelationDesign.idl @@ -49,7 +49,7 @@ published service RelationDesign /** is used to initialize the RelationDesign. <p>Parameters (passed to the method - <member scope="com::sun::star::lang">XInitialization::initialize</member>) + com::sun::star::lang::XInitialization::initialize()) have to be instances of com::sun::star::beans::PropertyValue, where the <member scope="com::sun::star::beans">PropertyValue::Name</member> member specifies what the parameter controls, with the <member scope="com::sun::star::beans">PropertyValue::Value</member> member containing the value diff --git a/offapi/com/sun/star/sdb/RowSet.idl b/offapi/com/sun/star/sdb/RowSet.idl index d1f3ec7172a1..e79f99341128 100644 --- a/offapi/com/sun/star/sdb/RowSet.idl +++ b/offapi/com/sun/star/sdb/RowSet.idl @@ -81,8 +81,8 @@ published interface XParametersSupplier; </tr> <tr><td valign="top"><em>operation done</em></td> <td valign="top">When the operation is done, you get a notification about this. It may be a - <member scope="com::sun::star::sdbc">XRowSetListener::cursorMoved</member> or a - <member scope="com::sun::star::sdbc">XRowSetListener::rowChanged</member> call or a + com::sun::star::sdbc::XRowSetListener::cursorMoved() or a + com::sun::star::sdbc::XRowSetListener::rowChanged() call or a XRowsChangeListener::rowsChanged() call. </td> </tr> @@ -147,13 +147,13 @@ published interface XParametersSupplier; </p> <h3>Deletions</h3> - <p>Via <member scope="com::sun::star::sdbc">XResultSetUpdate::deleteRow</member>, you can delete the current row of a + <p>Via com::sun::star::sdbc::XResultSetUpdate::deleteRow(), you can delete the current row of a RowSet. This deleted row then doesn't vanish immediately, but is still present, and subsequent calls to - <member scope="com::sun::star::sdbc">XResultSet::rowDeleted</member> will return <TRUE/>. The deleted row "vanishes" from + com::sun::star::sdbc::XResultSet::rowDeleted() will return <TRUE/>. The deleted row "vanishes" from the RowSet as soon as the cursor is moved away from it.<br/> As a consequence, the behavior of several other methods is affected:<br/> <dl> - <dt><member scope="com::sun::star::sdbc">XResultSet::getRow</member></dt> + <dt>com::sun::star::sdbc::XResultSet::getRow()</dt> <dd>returns the position of the cursor, which has not been changed by the deletion.</dd> <dt>com::sun::star::sdbc::XResultSet: <code>next</code>, <code>first</code>, <code>last</code>, <code>absolute</code>, @@ -164,25 +164,25 @@ published interface XParametersSupplier; <code>15</code>, followed by <code>next</code>, then your RowSet afterwards still is on row 15, since the deleted row vanished with the move operation.</dd> - <dt><member scope="com::sun::star::sdbc">XResultSet::refreshRow</member></dt> + <dt>com::sun::star::sdbc::XResultSet::refreshRow()</dt> <dd>will throw an exception when the cursor is on a deleted row.</dd> <dt>com::sun::star::sdbc::XRow: <code>getFoo</code></dt> <dd>will return an empty value when the cursor is on a deleted row.</dd> - <dt><member scope="com::sun::star::sdbcx">XRowLocate::getBookmark</member></dt> + <dt>com::sun::star::sdbcx::XRowLocate::getBookmark()</dt> <dd>will throw an exception when the cursor is on a deleted row.</dd> <dt>com::sun::star::sdbc::XRowUpdate: <code>updateFoo</code></dt> <dd>will throw an exception when the cursor is on a deleted row.</dd> - <dt><member scope="com::sun::star::sdbc">XResultSetUpdate::deleteRow</member></dt> + <dt>com::sun::star::sdbc::XResultSetUpdate::deleteRow()</dt> <dd>will throw an exception when the cursor is on a deleted row.</dd> - <dt><member scope="com::sun::star::sdbc">XResultSetUpdate::moveToInsertRow</member></dt> + <dt>com::sun::star::sdbc::XResultSetUpdate::moveToInsertRow()</dt> <dd>will let the deleted row vanish from the result set. As a consequence, the <member>RowCount</member> will decrease. Also, subsequent calls to - <member scope="com::sun::star::sdbc">XResultSetUpdate::moveToCurrentRow</member> will not + com::sun::star::sdbc::XResultSetUpdate::moveToCurrentRow() will not be able to move back to the deleted row (since it vanished), but only to the row after the deleted row.</dd> </dl> @@ -221,8 +221,8 @@ published service RowSet <p>The optional support of this interface is already implied with the support of the com::sun::star::sdbc::ResultSet service.</p> <p>However, note that the additional support of the XRowSetApproveBroadcaster interface results - in a semantical extension: the methods <member scope="com::sun::star::sdbc">XResultSetUpdate::insertRow</member>, - <member scope="com::sun::star::sdbc">XResultSetUpdate::updateRow</member> and <member scope="com::sun::star::sdbc">XResultSetUpdate::deleteRow</member> + in a semantical extension: the methods com::sun::star::sdbc::XResultSetUpdate::insertRow(), + com::sun::star::sdbc::XResultSetUpdate::updateRow() and com::sun::star::sdbc::XResultSetUpdate::deleteRow() will now throw the RowSetVetoException if the action which is to be performed was vetoed by one of the XRowSetApproveListener's.</p> */ @@ -233,7 +233,7 @@ published service RowSet <p>The optional support of this interface is already implied with the support of the com::sun::star::sdbcx::ResultSet service.</p> <p>However, note that the additional support of the XRowSetApproveBroadcaster interface results - in a semantical extension: the method <member scope="com::sun::star::sdbcx">XDeleteRows::deleteRows</member> + in a semantical extension: the method com::sun::star::sdbcx::XDeleteRows::deleteRows() will now throw the RowSetVetoException if the deletion was vetoed by one of the XRowSetApproveListener's.</p> */ diff --git a/offapi/com/sun/star/sdb/SingleSelectQueryAnalyzer.idl b/offapi/com/sun/star/sdb/SingleSelectQueryAnalyzer.idl index 3cbd15b9c4b6..4b701c9ff435 100644 --- a/offapi/com/sun/star/sdb/SingleSelectQueryAnalyzer.idl +++ b/offapi/com/sun/star/sdb/SingleSelectQueryAnalyzer.idl @@ -54,7 +54,7 @@ service SingleSelectQueryAnalyzer a query named <code>All Orders</code>, the SQL statement <code>SELECT * FROM "All Orders"</code> is perfectly valid when used with a SingleSelectQueryAnalyzer.</p> - <p>In this case, the name container returned by <member scope="com::sun::star::sdbcx">XTablesSupplier::getTables</member> + <p>In this case, the name container returned by com::sun::star::sdbcx::XTablesSupplier::getTables() will in fact not return a Table, but a Query object. Semantically, however, this object still acts as a table in the SQL statement.</p> diff --git a/offapi/com/sun/star/sdb/TableDesign.idl b/offapi/com/sun/star/sdb/TableDesign.idl index 46c2231a0852..e337c52e7450 100644 --- a/offapi/com/sun/star/sdb/TableDesign.idl +++ b/offapi/com/sun/star/sdb/TableDesign.idl @@ -49,7 +49,7 @@ published service TableDesign /** is used to initialize the TableDesign. <p>Parameters (passed to the method - <member scope="com::sun::star::lang">XInitialization::initialize</member>) + com::sun::star::lang::XInitialization::initialize()) have to be instances of com::sun::star::beans::PropertyValue, where the <member scope="com::sun::star::beans">PropertyValue::Name</member> member specifies what the parameter controls, with the <member scope="com::sun::star::beans">PropertyValue::Value</member> member containing the value diff --git a/offapi/com/sun/star/sdb/XDocumentDataSource.idl b/offapi/com/sun/star/sdb/XDocumentDataSource.idl index 4d1fc62495f3..33dbcdb4cc5e 100644 --- a/offapi/com/sun/star/sdb/XDocumentDataSource.idl +++ b/offapi/com/sun/star/sdb/XDocumentDataSource.idl @@ -42,7 +42,7 @@ interface XDocumentDataSource each of the two can exist without its counterpart, but create this counterpart on request only. As a consequence, the document obtained via this attribute might be newly created, which implies that the caller is now responsible for it. In particular, the caller is - responsible for calling <member scope="com::sun::star::util">XCloseable::close</member> + responsible for calling com::sun::star::util::XCloseable::close() on the document as soon as it's not needed anymore.</p> <p>Additionally, if the caller does long-lasting processing on the document, it's advised diff --git a/offapi/com/sun/star/sdb/application/XDatabaseDocumentUI.idl b/offapi/com/sun/star/sdb/application/XDatabaseDocumentUI.idl index d4a95a6e978f..55ee6c1cb743 100644 --- a/offapi/com/sun/star/sdb/application/XDatabaseDocumentUI.idl +++ b/offapi/com/sun/star/sdb/application/XDatabaseDocumentUI.idl @@ -68,7 +68,7 @@ interface XDatabaseDocumentUI of the application. Clients should not misuse it, in particular, closing the connection can yield unexpected results and should definitely be avoided. If you need a separate connection to the data source, use - <member scope="com::sun::star::sdbc">XDataSource::getConnection</member>.</p> + com::sun::star::sdbc::XDataSource::getConnection().</p> */ [attribute, readonly] com::sun::star::sdbc::XConnection ActiveConnection; @@ -80,7 +80,7 @@ interface XDatabaseDocumentUI <p>If the application is already connected, nothing happens. If it is not connected, the application will try to establish a connection by using - <member scope="com::sun::star::sdbc">XDataSource::getConnection</member> + com::sun::star::sdbc::XDataSource::getConnection() with the current settings, as specified in the <member scope="com::sun::star::sdb">DataSource::Settings</member> member.</p> @@ -138,7 +138,7 @@ interface XDatabaseDocumentUI <code>closeSubComponents</code>, which will gracefully do this.</p> <p>In a first step, the sub components will be suspended - (<member scope="com::sun::star::frame">XController::suspend</member>). There + (com::sun::star::frame::XController::suspend()). There are basically two reasons why suspending a single sub component can fail: The user might veto it (she's asked if the document is currently modified), and the component might be uncloseable currently, e.g. due to an open modal diff --git a/offapi/com/sun/star/sdb/tools/XObjectNames.idl b/offapi/com/sun/star/sdb/tools/XObjectNames.idl index dafa0eeb7057..c800dc1e9b60 100644 --- a/offapi/com/sun/star/sdb/tools/XObjectNames.idl +++ b/offapi/com/sun/star/sdb/tools/XObjectNames.idl @@ -44,7 +44,7 @@ module com { module sun { module star { module sdb { module tools { service.</p> <p>The component itself does not have life-time control mechanisms, i.e. you - cannot explicitly dispose it (<member scope="com::sun::star::lang">XComponent::dispose</member>), + cannot explicitly dispose it (com::sun::star::lang::XComponent::dispose()), and you cannot be notified when it dies.<br/> However, if your try to access any of its methods or attributes, after the connection which was used to create it was closed, a com::sun::star::lang::DisposedException diff --git a/offapi/com/sun/star/sdb/tools/XTableName.idl b/offapi/com/sun/star/sdb/tools/XTableName.idl index 5c96f75461e1..c6e55057c526 100644 --- a/offapi/com/sun/star/sdb/tools/XTableName.idl +++ b/offapi/com/sun/star/sdb/tools/XTableName.idl @@ -41,7 +41,7 @@ module com { module sun { module star { module sdb { module tools { names.</p> <p>The component itself does not have life-time control mechanisms, i.e. you - cannot explicitly dispose it (<member scope="com::sun::star::lang">XComponent::dispose</member>), + cannot explicitly dispose it (com::sun::star::lang::XComponent::dispose()), and you cannot be notified when it dies.<br/> However, if your try to access any of its methods or attributes, after the connection which was used to create it was closed, a com::sun::star::lang::DisposedException @@ -110,7 +110,7 @@ interface XTableName <p>Retrieving this attribute is equivalent to obtaining the tables container from the connection (via com::sun::star::sdbcx::XTablesSupplier), - and calling its <member scope="com::sun::star::container">XNameAccess::getByName</member> + and calling its com::sun::star::container::XNameAccess::getByName() method with the ComposedName.</p> @throws com::sun::star::container::NoSuchElementException diff --git a/offapi/com/sun/star/sdbc/XDatabaseMetaData.idl b/offapi/com/sun/star/sdbc/XDatabaseMetaData.idl index dbfef368b080..ec65d59f7a67 100644 --- a/offapi/com/sun/star/sdbc/XDatabaseMetaData.idl +++ b/offapi/com/sun/star/sdbc/XDatabaseMetaData.idl @@ -2360,7 +2360,7 @@ published interface XDatabaseMetaData: com::sun::star::uno::XInterface /** indicates whether or not a visible row insert can be detected by calling - <member scope="com::sun::star::sdbc">XResultSet::rowInserted().</member> + com::sun::star::sdbc::XResultSet::rowInserted().() @param setType defined in com::sun::star::sdbc::ResultSetType diff --git a/offapi/com/sun/star/sheet/XMultiFormulaTokens.idl b/offapi/com/sun/star/sheet/XMultiFormulaTokens.idl index d9760fb6802e..ea2af811986b 100644 --- a/offapi/com/sun/star/sheet/XMultiFormulaTokens.idl +++ b/offapi/com/sun/star/sheet/XMultiFormulaTokens.idl @@ -33,7 +33,7 @@ module com { module sun { module star { module sheet { A service implementing this interface can internally set an arbitrary number of formula token sequences. The number of allowed formula token sequences must be returned by the - <member scope="com::sun::star::sheet">XMultiFormulaTokens::getCount</member> + com::sun::star::sheet::XMultiFormulaTokens::getCount() method. When the client code tries to access formula tokens at index that is outside the allowed index range, the implementation shall return an <type scope="com::sun::star::lang">IndexOutOfBoundsException</member>. diff --git a/offapi/com/sun/star/text/MailMerge.idl b/offapi/com/sun/star/text/MailMerge.idl index 7f373c770635..b6a574dfc200 100644 --- a/offapi/com/sun/star/text/MailMerge.idl +++ b/offapi/com/sun/star/text/MailMerge.idl @@ -39,7 +39,7 @@ published service MailMerge { /** interface to execute the mail merge action. - <p>The <member scope="com::sun::star::task">XJob::execute</member> + <p>The com::sun::star::task::XJob::execute() method of the interface accepts exactly the same properties as provided by this service in its argument sequence.</p> @@ -103,7 +103,7 @@ published service MailMerge <p>Note that any superservices of com::sun::star::sdbc::ResultSet are also allowed. Especially, this member can denote an instance of the com::sun::star::sdb::RowSet, or an instance obtained - by calling <member scope="com::sun::star::sdb">XResultSetAccess::createResultSet</member> + by calling com::sun::star::sdb::XResultSetAccess::createResultSet() on such a com::sun::star::sdb::RowSet. This becomes important in conjunction with the <member>Selection</member> property.</p> diff --git a/offapi/com/sun/star/ucb/Content.idl b/offapi/com/sun/star/ucb/Content.idl index 745fd68b8258..1230e3f25b32 100644 --- a/offapi/com/sun/star/ucb/Content.idl +++ b/offapi/com/sun/star/ucb/Content.idl @@ -54,9 +54,9 @@ published service Content registered at the content ( the content holds the listeners ) and the implementation of the listener interface holds a reference on the content. If the content shall be released, - <member scope="com::sun::star::lang">XComponent::dispose</member> must + com::sun::star::lang::XComponent::dispose() must be called at the content. The implementation of this method must call - <member scope="com::sun::star::lang">XEventListener::disposing</member> + com::sun::star::lang::XEventListener::disposing() on the registered listeners and release the appropriate object references. At the other hand, the implementation of XEventListener::disposing must release its appropriate references. diff --git a/offapi/com/sun/star/ucb/ContentProviderProxy.idl b/offapi/com/sun/star/ucb/ContentProviderProxy.idl index b3c059b9eefc..3320affa5827 100644 --- a/offapi/com/sun/star/ucb/ContentProviderProxy.idl +++ b/offapi/com/sun/star/ucb/ContentProviderProxy.idl @@ -39,7 +39,7 @@ module com { module sun { module star { module ucb { published service ContentProviderProxy { /** The implementation of - <member scope="com::sun::star::uno">XInterface::queryInterface</member> + com::sun::star::uno::XInterface::queryInterface() must instantiate the real provider and return the return value of a queryInterface call at the real provider, except for queries for the interfaces implemented by the proxy itself. So the caller of diff --git a/offapi/com/sun/star/ucb/DefaultHierarchyDataSource.idl b/offapi/com/sun/star/ucb/DefaultHierarchyDataSource.idl index 7b86969d621b..bf795cc76499 100644 --- a/offapi/com/sun/star/ucb/DefaultHierarchyDataSource.idl +++ b/offapi/com/sun/star/ucb/DefaultHierarchyDataSource.idl @@ -36,7 +36,7 @@ published service DefaultHierarchyDataSource com::sun::star::configuration::ConfigurationProvider for reading and writing hierarchy data. - <p><member scope="com::sun::star::lang">XMultiServiceFactory::createInstanceWithArguments</member> + <p>com::sun::star::lang::XMultiServiceFactory::createInstanceWithArguments() supports the service specifiers <code>"com.sun.star.ucb.HierarchyDataReadAccess"</code> and <code>"com.sun.star.ucb.HierarchyDataReadWriteAccess"</code>. diff --git a/offapi/com/sun/star/ucb/HierarchyDataReadWriteAccess.idl b/offapi/com/sun/star/ucb/HierarchyDataReadWriteAccess.idl index 97b081a1eb87..3280f3c3795e 100644 --- a/offapi/com/sun/star/ucb/HierarchyDataReadWriteAccess.idl +++ b/offapi/com/sun/star/ucb/HierarchyDataReadWriteAccess.idl @@ -52,25 +52,25 @@ published service HierarchyDataReadWriteAccess /** gives access to all contents provided by this provider. - <p><member scope="com::sun::star::lang">XSingleServiceFactory::createInstance</member> + <p>com::sun::star::lang::XSingleServiceFactory::createInstance() will create a new empty hierarchy data node. After it was created it's data members can be filled. Last, the node can be inserted as child of another node using - <member scope="com::sun::star::container">XNameContainer::insertByName</member>. + com::sun::star::container::XNameContainer::insertByName(). <p>There are no special arguments that must be supported by - <member scope="com::sun::star::lang">XSingleServiceFactory::createInstanceWithArguments</member> + com::sun::star::lang::XSingleServiceFactory::createInstanceWithArguments() */ interface com::sun::star::lang::XSingleServiceFactory; /** allows managing changes within the hierarchy. - <p><member scope="com::sun::star::util">XChangesBatch::getPendingChanges</member> + <p>com::sun::star::util::XChangesBatch::getPendingChanges() reports all changes within the hierarchy that are done through (direct or indirect) descendants of this element. The same set of changes is committed to persistent storage and/or made visible to other objects accessing the same data set, when - <member scope="com::sun::star::util">XChangesBatch::commitChanges</member> + com::sun::star::util::XChangesBatch::commitChanges() is invoked. */ interface com::sun::star::util::XChangesBatch; diff --git a/offapi/com/sun/star/ucb/HierarchyDataSource.idl b/offapi/com/sun/star/ucb/HierarchyDataSource.idl index 072c0c038c13..0da7ea0f18b6 100644 --- a/offapi/com/sun/star/ucb/HierarchyDataSource.idl +++ b/offapi/com/sun/star/ucb/HierarchyDataSource.idl @@ -41,7 +41,7 @@ published service HierarchyDataSource fragments of the hierarchy data. <p>The parameter <var>aServiceSpecifier</var> passed to - <member scope="com::sun::star::lang">XMultiServiceFactory::createInstanceWithArguments</member> + com::sun::star::lang::XMultiServiceFactory::createInstanceWithArguments() supports at least the service specifier <code>"com.sun.star.ucb.HierarchyDataReadAccess"</code>, which will create a <b>read-only view</b> to the data. The object that is created @@ -50,12 +50,12 @@ published service HierarchyDataSource <p><b>Optionally</b> the factory may support <b>writable views</b>. A writable view is requested by passing the service specifier <code>"com.sun.star.ucb.HierarchyDataReadWriteAccess"</code> to - <member scope="com::sun::star::lang">XMultiServiceFactory::createInstanceWithArguments</member> + com::sun::star::lang::XMultiServiceFactory::createInstanceWithArguments() The object that is created implements the service HierarchyDataReadWriteAccess. <p>The arguments passed to - <member scope="com::sun::star::lang">XMultiServiceFactory::createInstanceWithArguments</member> + com::sun::star::lang::XMultiServiceFactory::createInstanceWithArguments() in parameter <var>aArguments</var> specify the view of the data that should be created. That is, they determine the subset of elements that can be accessed starting from the returned object. Each element of the @@ -81,9 +81,9 @@ published service HierarchyDataSource <p>An implementation must ignore unknown arguments. <p>The implementation of - <member scope="com::sun::star::lang">XMultiServiceFactory::createInstance</member> + com::sun::star::lang::XMultiServiceFactory::createInstance() must behave exactly as if - <member scope="com::sun::star::lang">XMultiServiceFactory::createInstanceWithArguments</member> + com::sun::star::lang::XMultiServiceFactory::createInstanceWithArguments() were called passing one single property named <code>nodepath</code> where the property value is an empty string. Thus it always creates a view to the root of the hierarchy data. diff --git a/offapi/com/sun/star/ucb/XDynamicResultSet.idl b/offapi/com/sun/star/ucb/XDynamicResultSet.idl index 6fd0d57a10d9..6df0bc3089f4 100644 --- a/offapi/com/sun/star/ucb/XDynamicResultSet.idl +++ b/offapi/com/sun/star/ucb/XDynamicResultSet.idl @@ -112,9 +112,9 @@ published interface XDynamicResultSet: com::sun::star::lang::XComponent /** Call this, if you want to get notifications about changes. <p>The implementor has to call - <member scope="com::sun::star::lang">XComponent::addEventListener</member> + com::sun::star::lang::XComponent::addEventListener() in this method, so that we can call - <member scope="com::sun::star::lang">XEventListener::disposing</member> + com::sun::star::lang::XEventListener::disposing() at the listener @param Listener diff --git a/offapi/com/sun/star/ucb/XInteractionSupplyAuthentication.idl b/offapi/com/sun/star/ucb/XInteractionSupplyAuthentication.idl index c5d719b1f048..28f0ff3ee9b2 100644 --- a/offapi/com/sun/star/ucb/XInteractionSupplyAuthentication.idl +++ b/offapi/com/sun/star/ucb/XInteractionSupplyAuthentication.idl @@ -40,7 +40,7 @@ published interface XInteractionSupplyAuthentication: com::sun::star::task::XInt /** Set a new "realm" value to hand back. <p>This method should be called before - <member scope="com::sun::star::task">XInteractionContinuation::select</member>, + com::sun::star::task::XInteractionContinuation::select(), and should only be called if XInteractionSupplyAuthentication::canSetRealm() returned <true/>.</p> @@ -54,7 +54,7 @@ published interface XInteractionSupplyAuthentication: com::sun::star::task::XInt /** Set a new "user name" value to hand back. <p>This method should be called before - <member scope="com::sun::star::task">XInteractionContinuation::select</member>, + com::sun::star::task::XInteractionContinuation::select(), and should only be called if XInteractionSupplyAuthentication::canSetUserName() returned <true/>.</p> @@ -68,7 +68,7 @@ published interface XInteractionSupplyAuthentication: com::sun::star::task::XInt /** Set a new "password" value to hand back. <p>This method should be called before - <member scope="com::sun::star::task">XInteractionContinuation::select</member>, + com::sun::star::task::XInteractionContinuation::select(), and should only be called if XInteractionSupplyAuthentication::canSetPassword() returned <true/>.</p> @@ -90,7 +90,7 @@ published interface XInteractionSupplyAuthentication: com::sun::star::task::XInt /** Set a new mode of how long to remember the password. <p>This method should be called before - <member scope="com::sun::star::task">XInteractionContinuation::select</member>, + com::sun::star::task::XInteractionContinuation::select(), and should only be called if XInteractionSupplyAuthentication::setPassword() is also called.</p> @@ -108,7 +108,7 @@ published interface XInteractionSupplyAuthentication: com::sun::star::task::XInt /** Set a new "account" value to hand back. <p>This method should be called before - <member scope="com::sun::star::task">XInteractionContinuation::select</member>, + com::sun::star::task::XInteractionContinuation::select(), and should only be called if XInteractionSupplyAuthentication::canSetAccount() returned <true/>.</p> @@ -130,7 +130,7 @@ published interface XInteractionSupplyAuthentication: com::sun::star::task::XInt /** Set a new mode of how long to remember the account. <p>This method should be called before - <member scope="com::sun::star::task">XInteractionContinuation::select</member>, + com::sun::star::task::XInteractionContinuation::select(), and should only be called if XInteractionSupplyAuthentication::setAccount() is also called.</p> diff --git a/offapi/com/sun/star/ucb/XUniversalContentBroker.idl b/offapi/com/sun/star/ucb/XUniversalContentBroker.idl index 4d971316243b..6df4b2f46758 100644 --- a/offapi/com/sun/star/ucb/XUniversalContentBroker.idl +++ b/offapi/com/sun/star/ucb/XUniversalContentBroker.idl @@ -40,10 +40,10 @@ published interface XUniversalContentBroker <p>Those references i.e. may occur if content provider implementations hold references to the Broker. The Broker itself always holds its providers. If the Broker shall be released, - <member scope="com::sun::star::lang">XComponent::dispose</member> + com::sun::star::lang::XComponent::dispose() must be called at the Broker. The implementation of this method must call - <member scope="com::sun::star::lang">XEventListener::disposing</member> + com::sun::star::lang::XEventListener::disposing() on the registered listeners (the providers holding the Broker must be those listeners) and release the appropriate object references. At the other hand, the implementation of XEventListener::disposing must diff --git a/offapi/com/sun/star/ui/XImageManager.idl b/offapi/com/sun/star/ui/XImageManager.idl index 54971113dd7c..f825534d0557 100644 --- a/offapi/com/sun/star/ui/XImageManager.idl +++ b/offapi/com/sun/star/ui/XImageManager.idl @@ -177,7 +177,7 @@ interface XImageManager is placed into the <member scope="com::sun::star::ui">ConfigurationEvent::Element</member>. The image set which has been changed is put into the - <member scope="com::sun::star::ui">ConfigurationEvent::aInfo</member>. + com::sun::star::ui::ConfigurationEvent::aInfo(). </p> */ interface com::sun::star::ui::XUIConfiguration; diff --git a/offapi/com/sun/star/xforms/XSubmission.idl b/offapi/com/sun/star/xforms/XSubmission.idl index ea070392bec6..ee5dba1764bb 100644 --- a/offapi/com/sun/star/xforms/XSubmission.idl +++ b/offapi/com/sun/star/xforms/XSubmission.idl @@ -44,7 +44,7 @@ interface XSubmission /** allows the submission to be associated with certain form controls - <p>Calling the <member scope="com::sun::star::form::submission">XSubmission::submit</member> + <p>Calling the com::sun::star::form::submission::XSubmission::submit() yields exactly the same result as calling XModel::submit() of the model which the submission belongs to, passing the ID of the submission.</p> */ |