-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning message "Found unknown folders in the input file: activeX" #1202
Comments
Hi @DataConnection , thanks for the kind words! I assume you want the activeX element preserved? Unfortunately there is a minor issue here: Could you have a look if #1204 works for you? Since it is unlikely that I ever want to modify the activeX subfolder (or even want to understand its contents), I simply copy the contents from the original file when saving it. If you have access to - please also try if this works with files with more activeX elements. You can install it like this: remotes::install_github("JanMarvin/openxlsx2#1204") |
Hi @JanMarvin, thank you very much for your fast reaction and the fix. Saving with wb_save and reopening in Excel loses some functionality - I get
It looks like some properties of activeX elements (i.e. LinkedCell on InputBox) get lost. Thanks again for your great work, we use openxlsx2 a lot. Best Wolf |
Thanks for the reply! Obviously loading and saving the file correctly is the goal :) Since I'm not familiar with activeX in spreadsheets, does this work in MS365 on Windows and if yes, how can I reproduce this? |
Yes - now opening the file in Office2021 on Windows works without complains (have no MS365). Great work! |
Perfect! Thanks for the follow up |
Hi,
I get the warning message on opening the attached excel file - activeX-element.xlsx.
It was generated in Excel - an empty file, with just one activeX element added (in Excel from ribbon "Developer tools").
Probably similar to #1012
Thanks for fixing it - no need to hurry - and thanks for your great work!
Wolf
The text was updated successfully, but these errors were encountered: