Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


If your code applies to a certain type of  spreadsheet:
Create a new template with predefined names, database ranges, styles and
your macros.
Let the code work conveniently with the predefined items. This will save you
hundreds of lines of Basic. Every new document derived from that template
will inherit all the predefined items and the code.
When you modify some style, the changes apply instantly to all the styled
cells and you don't have to change a single line of code. 

If you try to develop generic code that applies to different types of 
spreadsheet you should dive deeply into the API documentation and install an
object inspector. I recommend the MRI extension.

I use to auto-format spreadsheets by means of conditional formatting and/or
function STYLE. I never need any macros for this.

--
View this message in context: 
http://nabble.documentfoundation.org/Setting-format-code-in-macro-tp3298838p3299435.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.