1/************************************************************** 2 * 3 * Licensed to the Apache Software Foundation (ASF) under one 4 * or more contributor license agreements. See the NOTICE file 5 * distributed with this work for additional information 6 * regarding copyright ownership. The ASF licenses this file 7 * to you under the Apache License, Version 2.0 (the 8 * "License"); you may not use this file except in compliance 9 * with the License. You may obtain a copy of the License at 10 * 11 * http://www.apache.org/licenses/LICENSE-2.0 12 * 13 * Unless required by applicable law or agreed to in writing, 14 * software distributed under the License is distributed on an 15 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY 16 * KIND, either express or implied. See the License for the 17 * specific language governing permissions and limitations 18 * under the License. 19 * 20 *************************************************************/ 21 22 23#ifndef __com_sun_star_bridge_oleautomation_PropertyPutArgument_idl__ 24#define __com_sun_star_bridge_oleautomation_PropertyPutArgument_idl__ 25 26 27module com { module sun { module star { module bridge { module oleautomation { 28 29/** contains a value that is used as argument in a "property put" 30 operation on a Automation object. 31 <p> 32 If a Automation object is converted into a UNO object by a scripting 33 bridge, such as 34 <type scope="com::sun::star::bridge::oleautomation">BridgeSupplier</type>, 35 then it is accessed through the 36 <type scope="com::sun::star::script">XInvocation</type> interface. 37 The methods 38 <member scope="com::sun::star::script">XInvocation::setValue</member> 39 and 40 <member scope="com::sun::star::script">XInvocation::getValue</member> 41 are used to access properties which do not have additional 42 arguments. To access a property with additional arguments, the 43 method 44 <member scope="com::sun::star::script">XInvocation::invoke</member> 45 has to be used. The method implementation must decide, if the 46 property is to be written or read so it can perform the proper 47 operation on the Automation object. To make this decision, the 48 caller has to provide the information if the current call is 49 intended to be a write or read operation. This is done by 50 providing either instances of <type>PropertyPutArgument</type> or 51 <type>PropertyGetArgument</type> as arguments to 52 <member scope="com::sun::star::script">XInvocation::Invoke</member>. 53 54 @since OpenOffice 1.1.2 55*/ 56struct PropertyPutArgument 57{ 58 /** contains the actual argument. 59 */ 60 any Value; 61}; 62 63}; }; }; }; }; 64 65 66#endif 67