On 7/5/19 9:39 PM, Virgil Arrington wrote:
To my knowledge, that sort of thing doesn't happen with LO, making reveal codes unnecessary.
In general, I agree with you.
However, there were one or two times when the RevealCodes4Cal macro
showed me what was going wrong with the styles in the cells, that
Stylist was not displaying, or otherwise telling me.
I never found the standard reveal codes useful. Much simpler to simply
export the document to plain text, then open it as a plain text file,
then add the appropriate formatting, than mess around with what styles
might, or more often might not have been used.
To me, using reveal codes in LO is like trying to use a gas gauge on an electric car.
https://www.youtube.com/watch?v=j52odgkRxDs
and that is not the only video on YouTube showing somebody trying to
figure out where to put gas into their Tesla.
###
It looks like I don't have a copy of thae RevealCodes4Calc macro anymore.
jonathon
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
- Re: [libreoffice-users] Reveal code, old macros convert them to LO (continued)
Re: [libreoffice-users] Reveal code, old macros convert them to LO · jomali
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.