Bug 134829 - Gotorange method gives an error pointing to a textsection with only a texttable as content
Summary: Gotorange method gives an error pointing to a textsection with only a texttab...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-15 10:35 UTC by Clésio Pinheiro
Modified: 2024-05-04 03:17 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
File to test (9.38 KB, application/vnd.oasis.opendocument.text)
2020-07-15 10:35 UTC, Clésio Pinheiro
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Clésio Pinheiro 2020-07-15 10:35:35 UTC
Created attachment 163056 [details]
File to test

When using a macro in Writer to point to a textsection, if the only content of this testsection is a texttable, the gotorange method gives this error:
"Erro de execução do BASIC.
Ocorreu uma exceção 
Type: com.sun.star.uno.RuntimeException
Message: ."

My macro goes like this:

Sub Main
	dim file,section, oAnchor, textcursor
	file = thiscomponent
	textcursor = file.getText().createTextCursor()
	if file.getTextSections.hasByName("Seção1") then
		section = file.getTextSections.getByName("Seção1")
		oAnchor = section.getAnchor()
		textcursor.gotoRange(oAnchor, False)
	end if
End Sub
Comment 1 Xisco Faulí 2020-08-03 14:53:08 UTC
Thanks for reporting this issue.
Did the macro work in the past ? Which version of LibreOffice did it work with ?
Comment 2 Clésio Pinheiro 2020-08-03 17:56:34 UTC
It is a new macro, so i really don't know if it could have worked in older versions.
Comment 3 QA Administrators 2020-08-04 04:20:04 UTC Comment hidden (obsolete)
Comment 4 Clésio Pinheiro 2020-08-04 07:27:53 UTC
The funny thing is that if that textsection has a space or a paragraph besides the texttable, the macro works.
Comment 5 Buovjaga 2021-01-18 17:51:00 UTC
Alain: can you give your opinion?
Comment 6 Xisco Faulí 2022-05-02 12:15:57 UTC
A new major release of LibreOffice is available since this bug was reported.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 7 Andreas Heinisch 2022-05-04 18:38:44 UTC
Still in: 
Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: a58701650c2dd7ad8514752d571aa2569690fe37
CPU threads: 6; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: de-DE (de_DE); UI: en-US
Calc: CL
Comment 8 QA Administrators 2024-05-04 03:17:08 UTC
Dear Clésio Pinheiro,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug