Description: Attached example file contains a VBA macro that is supposed to switch the currently activated open file. This does not happen, all we get is a NoSuchElementException. Steps to Reproduce: 1. Download the attached files to the c:\TEMP directory 2. Open the example file and try to run the FileOpenExample macro Actual Results: Execution of the macro is stopped at the Activate call. Expected Results: The file is activated as in Excel. Reproducible: Always User Profile Reset: No Additional Info: LibreOffice details: Version: 6.4.0.0.alpha0+ (x86) Build ID: 49422a469646ad8be43ba828ca24c2484c26b9e8 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-07-08_00:50:19 Locale: hu-HU (hu_HU); UI-Language: en-US Calc: CL
Created attachment 152845 [details] Example file from Excel with the macro
Created attachment 152846 [details] Example file to open by the macro
Created attachment 152847 [details] Example file to open by the macro
Created attachment 152848 [details] Screenshot of the original document in Calc
Confirm with Version: 6.4.0.0.alpha0+ Build ID: 47a774fbef8c224e4853de3fdd0230b9442bb716 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Dear NISZ LibreOffice Team, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The macro works in excel using: Public Sub FileOpenExample() file1 = "C:\temp\Example.xlsx" file2 = "C:\temp\Example1.xlsx" Workbooks.Open Filename:=file1 Workbooks.Open Filename:=file2 Windows("Example.xlsx").Activate Windows("Example1.xlsx").Activate End Sub I could not get it to work using your macro: Public Sub FileOpenExample() file1 = "C:\temp\Example.xlsx" file2 = "C:\temp\Example1.xlsx" Workbooks.Open Filename:=file1 Workbooks.Open Filename:=file2 Windows(file1).Activate Windows(file2).Activate End Sub Did I something wrong?
Andreas Heinisch committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/deb0bb9f2635a8dfec90b42e3727f4224548a8e9 tdf#126457 - Add URL and workbook name to window titles It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.