LibreOffice - Revision history

Water: /* Tools */

2026-03-04T16:17:34Z

Tools

← Older revision		Revision as of 16:17, 4 March 2026
Line 231:		Line 231:

	==Tools==		==Tools==
	~~To be defined~~.		This forum thread describes [https://www.autoitscript.com/forum/topic/213493-au3-libreoffice-api-inspector-tools/ LibreOffice API Inspector tools]. <br>They allow you to inspect Object and properties in the LibreOffice API.

	==References==		==References==
	* [https://wiki.documentfoundation.org/Documentation/DevGuide/Glossary LibreOffice Developer's Guide: Glossary]		* [https://wiki.documentfoundation.org/Documentation/DevGuide/Glossary LibreOffice Developer's Guide: Glossary]
	* [https://api.libreoffice.org/docs/idl/ref/index.html LibreOffice 24.2 SDK API Reference]		* [https://api.libreoffice.org/docs/idl/ref/index.html LibreOffice 24.2 SDK API Reference]

Water: /* Catching COM Errors */

2026-02-26T07:02:42Z

Catching COM Errors

← Older revision		Revision as of 07:02, 26 February 2026
Line 215:		Line 215:
	This UDF has user-COM error functions that allow the user to have a custom user function be called each time a COM error is encountered, or optionally, to either use MsgBox or ConsoleWrite to display the COM error details.<br>		This UDF has user-COM error functions that allow the user to have a custom user function be called each time a COM error is encountered, or optionally, to either use MsgBox or ConsoleWrite to display the COM error details.<br>
	Instructions for this are found in each respective COM Error function. Each component has its own dedicated COM user error handler, e.g., LibreOfficeWriter has the ''_LOWriter_ComError_UserFunction'', and also LibreOffice.au3 has its own COM error handler, called: ''_LO_ComError_UserFunction''. <br> A COM error error handler can display the following information about a COM error: Number, Description, At line, Source, Error Description, though it will not always have all of the values filled in.		Instructions for this are found in each respective COM Error function. Each component has its own dedicated COM user error handler, e.g., LibreOfficeWriter has the ''_LOWriter_ComError_UserFunction'', and also LibreOffice.au3 has its own COM error handler, called: ''_LO_ComError_UserFunction''. <br> A COM error error handler can display the following information about a COM error: Number, Description, At line, Source, Error Description, though it will not always have all of the values filled in.
	<br>If no ComError_UserFunction has been defined by the ~~Skript, LibreOffice~~ does nothing but handle the COM error, so your script does not crash and ~~set~~ @error and @extended.		<br>If no ComError_UserFunction has been defined, the UDF does nothing but handle the COM error, so your script does not crash, and sets the @error and @extended values.

	Example output:		Example output:

Water: Removed the WIP (work in progress) tag.

2026-02-25T15:24:06Z

Removed the WIP (work in progress) tag.

← Older revision		Revision as of 15:24, 25 February 2026
Line 1:		Line 1:
	~~{{WIP}}~~
	This article uses material from the Wikipedia article "[https://en.wikipedia.org/wiki/LibreOffice LibreOffice]" and other Wikipedia articles, which are released under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-Share-Alike License 4.0].		This article uses material from the Wikipedia article "[https://en.wikipedia.org/wiki/LibreOffice LibreOffice]" and other Wikipedia articles, which are released under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-Share-Alike License 4.0].

Water: Added FAQ and Tools section

2026-02-25T15:22:44Z

Added FAQ and Tools section

← Older revision		Revision as of 15:22, 25 February 2026
Line 227:		Line 227:
	'''Error Description:''' <br>		'''Error Description:''' <br>
	</blockquote>		</blockquote>

			==FAQ==
			There have been no frequently asked questions so far.

			==Tools==
			To be defined.

	==References==		==References==
	* [https://wiki.documentfoundation.org/Documentation/DevGuide/Glossary LibreOffice Developer's Guide: Glossary]		* [https://wiki.documentfoundation.org/Documentation/DevGuide/Glossary LibreOffice Developer's Guide: Glossary]
	* [https://api.libreoffice.org/docs/idl/ref/index.html LibreOffice 24.2 SDK API Reference]		* [https://api.libreoffice.org/docs/idl/ref/index.html LibreOffice 24.2 SDK API Reference]

Water at 08:46, 25 February 2026

2026-02-25T08:46:21Z

← Older revision		Revision as of 08:46, 25 February 2026
Line 211:		Line 211:

	* 6. '''Version errors'''. This code indicates that the current version of LibreOffice is too low for a specific function or parameter.<br> Any version limitations are documented in the function or parameter description. Either do not use the function or parameter that requires a higher LibreOffice version, or upgrade to a newer version of LibreOffice. <br>''Example:'' @error = 6 and @extended = 1 stands for: ''Current Libre Office version less than 7.4.''		* 6. '''Version errors'''. This code indicates that the current version of LibreOffice is too low for a specific function or parameter.<br> Any version limitations are documented in the function or parameter description. Either do not use the function or parameter that requires a higher LibreOffice version, or upgrade to a newer version of LibreOffice. <br>''Example:'' @error = 6 and @extended = 1 stands for: ''Current Libre Office version less than 7.4.''

	~~<br> **************************************<br>~~

	===Catching COM Errors===		===Catching COM Errors===

Water: /* Catching COM Errors */

2026-02-25T08:44:49Z

Catching COM Errors

← Older revision		Revision as of 08:44, 25 February 2026
Line 217:		Line 217:
	A further step in debugging scripts is to monitor for COM errors, which can be triggered if something fails on the LibreOffice side.<br>		A further step in debugging scripts is to monitor for COM errors, which can be triggered if something fails on the LibreOffice side.<br>
	This UDF has user-COM error functions that allow the user to have a custom user function be called each time a COM error is encountered, or optionally, to either use MsgBox or ConsoleWrite to display the COM error details.<br>		This UDF has user-COM error functions that allow the user to have a custom user function be called each time a COM error is encountered, or optionally, to either use MsgBox or ConsoleWrite to display the COM error details.<br>
	Instructions for this are found in each respective COM Error function. Each component has its own dedicated COM user error handler, e.g., LibreOfficeWriter has the ''_LOWriter_ComError_UserFunction'', and also LibreOffice.au3 has its own COM error handler ~~also~~, called: ''_LO_ComError_UserFunction''. <br> A COM error error handler can display the following information about a COM error: Number, Description, At line, Source, Error Description, though it will not always have all of the values filled in.		Instructions for this are found in each respective COM Error function. Each component has its own dedicated COM user error handler, e.g., LibreOfficeWriter has the ''_LOWriter_ComError_UserFunction'', and also LibreOffice.au3 has its own COM error handler, called: ''_LO_ComError_UserFunction''. <br> A COM error error handler can display the following information about a COM error: Number, Description, At line, Source, Error Description, though it will not always have all of the values filled in.
	<br>If no ComError_UserFunction has been defined by the Skript, LibreOffice does nothing but handle the COM error, so your script does not crash and set @error and @extended.		<br>If no ComError_UserFunction has been defined by the Skript, LibreOffice does nothing but handle the COM error, so your script does not crash and set @error and @extended.

Water: /* Catching COM Errors */

2026-02-25T08:34:43Z

Catching COM Errors

← Older revision		Revision as of 08:34, 25 February 2026
Line 216:		Line 216:
	===Catching COM Errors===		===Catching COM Errors===
	A further step in debugging scripts is to monitor for COM errors, which can be triggered if something fails on the LibreOffice side.<br>		A further step in debugging scripts is to monitor for COM errors, which can be triggered if something fails on the LibreOffice side.<br>
	This UDF has user-COM error functions that allow the user to have a custom user function be called each time a COM error is encountered, or optionally, to either use MsgBox or ConsoleWrite to display the COM error details. Instructions for this are found in each respective COM Error function~~, ''_LO_ComError_UserFunction'', ''_LOBase_ComError_UserFunction'', ''_LOCalc_ComError_UserFunction'', ''_LOWriter_ComError_UserFunction''~~. Each component has its own dedicated COM user error handler, e.g., LibreOfficeWriter has the ''_LOWriter_ComError_UserFunction		This UDF has user-COM error functions that allow the user to have a custom user function be called each time a COM error is encountered, or optionally, to either use MsgBox or ConsoleWrite to display the COM error details.<br>
	~~'', LibreOfficeCalc has ''_LOCalc_ComError_UserFunction~~'', and also LibreOffice.au3 has its own COM error handler also, called: ''_LO_ComError_UserFunction''. ~~This allows the user to further see when something is failing, and what may be the cause of the failure, and perhaps be able to correct it. The resulting~~ COM error ~~will always contain~~ the following ~~sections,~~ Number, Description, At line, Source, Error Description, though it will not always have all of the values filled in. ~~As an example, a COM error will look similar to the following:~~		Instructions for this are found in each respective COM Error function. Each component has its own dedicated COM user error handler, e.g., LibreOfficeWriter has the ''_LOWriter_ComError_UserFunction'', and also LibreOffice.au3 has its own COM error handler also, called: ''_LO_ComError_UserFunction''. <br> A COM error error handler can display the following information about a COM error: Number, Description, At line, Source, Error Description, though it will not always have all of the values filled in.
			<br>If no ComError_UserFunction has been defined by the Skript, LibreOffice does nothing but handle the COM error, so your script does not crash and set @error and @extended.
	~~-----~~
	; If ~~not~~ defined ~~ComError_UserFunction then this function~~ does nothing, ~~in which case you can only check~~ @error / @extended ~~after suspect functions~~.
	~~-----~~

			Example output:
	<blockquote>		<blockquote>
	! We intercepted a COM Error<br>		! We intercepted a COM Error<br>
	'''Number:''' 0x80020006<br>		'''Number:''' 0x80020006<br>
	'''Description:''' Unknown name.<br>		'''Description:''' Unknown name.<br>

	'''At line:''' 199<br>		'''At line:''' 199<br>
	'''Source:''' <br>		'''Source:''' <br>
	'''Error Description:''' <br>		'''Error Description:''' <br>
	</blockquote>		</blockquote>

	~~! We intercepted a COM Error<br>~~
	~~Number: 0x80020009<br>~~
	~~Description: Exception occurred.<br>~~
	~~At line: 200<br>~~
	~~Source: [automation bridge] <br>~~
	~~Error Description: InterfaceOleWrapper::Invoke : <br>~~
	~~[automation bridge]UnoConversionUtilities<T>::variantToAny <br>~~
	~~Cannot convert the value of vartype :"8" to the expected UNO type of type class: 6 at C:\cygwin64\home\buildslave\source\libo-core\extensions\source\ole\unoconversionutilities.hxx:590<br>~~
	~~-2147352567 0~~

	==References==		==References==
	* [https://wiki.documentfoundation.org/Documentation/DevGuide/Glossary LibreOffice Developer's Guide: Glossary]		* [https://wiki.documentfoundation.org/Documentation/DevGuide/Glossary LibreOffice Developer's Guide: Glossary]
	* [https://api.libreoffice.org/docs/idl/ref/index.html LibreOffice 24.2 SDK API Reference]		* [https://api.libreoffice.org/docs/idl/ref/index.html LibreOffice 24.2 SDK API Reference]

Water: Water moved page Libreoffice-WIP to LibreOffice

2026-02-25T08:11:51Z

Water moved page Libreoffice-WIP to LibreOffice

← Older revision	Revision as of 08:11, 25 February 2026
(No difference)

Water: /* Catching COM Errors */

2026-02-24T08:37:51Z

Catching COM Errors

← Older revision		Revision as of 08:37, 24 February 2026
Line 218:		Line 218:
	This UDF has user-COM error functions that allow the user to have a custom user function be called each time a COM error is encountered, or optionally, to either use MsgBox or ConsoleWrite to display the COM error details. Instructions for this are found in each respective COM Error function, ''_LO_ComError_UserFunction'', ''_LOBase_ComError_UserFunction'', ''_LOCalc_ComError_UserFunction'', ''_LOWriter_ComError_UserFunction''. Each component has its own dedicated COM user error handler, e.g., LibreOfficeWriter has the ''_LOWriter_ComError_UserFunction		This UDF has user-COM error functions that allow the user to have a custom user function be called each time a COM error is encountered, or optionally, to either use MsgBox or ConsoleWrite to display the COM error details. Instructions for this are found in each respective COM Error function, ''_LO_ComError_UserFunction'', ''_LOBase_ComError_UserFunction'', ''_LOCalc_ComError_UserFunction'', ''_LOWriter_ComError_UserFunction''. Each component has its own dedicated COM user error handler, e.g., LibreOfficeWriter has the ''_LOWriter_ComError_UserFunction
	'', LibreOfficeCalc has ''_LOCalc_ComError_UserFunction'', and also LibreOffice.au3 has its own COM error handler also, called: ''_LO_ComError_UserFunction''. This allows the user to further see when something is failing, and what may be the cause of the failure, and perhaps be able to correct it. The resulting COM error will always contain the following sections, Number, Description, At line, Source, Error Description, though it will not always have all of the values filled in. As an example, a COM error will look similar to the following:		'', LibreOfficeCalc has ''_LOCalc_ComError_UserFunction'', and also LibreOffice.au3 has its own COM error handler also, called: ''_LO_ComError_UserFunction''. This allows the user to further see when something is failing, and what may be the cause of the failure, and perhaps be able to correct it. The resulting COM error will always contain the following sections, Number, Description, At line, Source, Error Description, though it will not always have all of the values filled in. As an example, a COM error will look similar to the following:

			-----
			; If not defined ComError_UserFunction then this function does nothing, in which case you can only check @error / @extended after suspect functions.
			-----

	<blockquote>		<blockquote>

Water: /* Troubleshooting */

2026-02-24T08:20:35Z

Troubleshooting

← Older revision		Revision as of 08:20, 24 February 2026
Line 215:		Line 215:

	===Catching COM Errors===		===Catching COM Errors===
	A further step ~~for~~ debugging scripts is to monitor for COM errors, which can be triggered if something ~~is failing~~ on the LibreOffice side ~~of things~~. ~~To aid in monitoring for COM errors, this~~ UDF has user-COM error functions that allow the user to have a custom user function be called each time a COM error is encountered, or optionally, to either display ~~a MsgBox with~~ the COM error details~~, or output the COM error to the output using ConsoleWrite~~. Instructions for this are found in each respective COM Error function, ''_LO_ComError_UserFunction'', ''_LOBase_ComError_UserFunction'', ''_LOCalc_ComError_UserFunction'', ''_LOWriter_ComError_UserFunction''. Each component has its own dedicated COM user error handler, e.g., LibreOfficeWriter has the ''_LOWriter_ComError_UserFunction'', LibreOfficeCalc has ''_LOCalc_ComError_UserFunction'', and also LibreOffice.au3 has its own COM error handler also, called: ''_LO_ComError_UserFunction''. This allows the user to further see when something is failing, and what may be the cause of the failure, and perhaps be able to correct it. The resulting COM error will always contain the following sections, Number, Description, At line, Source, Error Description, though it will not always have all of the values filled in. As an example, a COM error will look similar to the following:		A further step in debugging scripts is to monitor for COM errors, which can be triggered if something fails on the LibreOffice side.<br>
			This UDF has user-COM error functions that allow the user to have a custom user function be called each time a COM error is encountered, or optionally, to either use MsgBox or ConsoleWrite to display the COM error details. Instructions for this are found in each respective COM Error function, ''_LO_ComError_UserFunction'', ''_LOBase_ComError_UserFunction'', ''_LOCalc_ComError_UserFunction'', ''_LOWriter_ComError_UserFunction''. Each component has its own dedicated COM user error handler, e.g., LibreOfficeWriter has the ''_LOWriter_ComError_UserFunction
			'', LibreOfficeCalc has ''_LOCalc_ComError_UserFunction'', and also LibreOffice.au3 has its own COM error handler also, called: ''_LO_ComError_UserFunction''. This allows the user to further see when something is failing, and what may be the cause of the failure, and perhaps be able to correct it. The resulting COM error will always contain the following sections, Number, Description, At line, Source, Error Description, though it will not always have all of the values filled in. As an example, a COM error will look similar to the following:

	<blockquote>		<blockquote>
Line 236:		Line 238:
	Cannot convert the value of vartype :"8" to the expected UNO type of type class: 6 at C:\cygwin64\home\buildslave\source\libo-core\extensions\source\ole\unoconversionutilities.hxx:590<br>		Cannot convert the value of vartype :"8" to the expected UNO type of type class: 6 at C:\cygwin64\home\buildslave\source\libo-core\extensions\source\ole\unoconversionutilities.hxx:590<br>
	-2147352567 0		-2147352567 0


	==References==		==References==
	* [https://wiki.documentfoundation.org/Documentation/DevGuide/Glossary LibreOffice Developer's Guide: Glossary]		* [https://wiki.documentfoundation.org/Documentation/DevGuide/Glossary LibreOffice Developer's Guide: Glossary]
	* [https://api.libreoffice.org/docs/idl/ref/index.html LibreOffice 24.2 SDK API Reference]		* [https://api.libreoffice.org/docs/idl/ref/index.html LibreOffice 24.2 SDK API Reference]