This chapter discusses how and where macro libraries are stored, along with methods you can use to manipulate them. This chapter also covers the subtleties of the macro organizer as well as using the UNO API to manipulate libraries and modules.
This chapter assumes a basic understanding of library containers, libraries, and modules. If the following summary is not familiar, review the material presented in Chapter 1, "Getting Started."
A library container contains zero or more libraries.
Each library contains zero or more modules and dialogs.
Each module contains zero or more macros.
The application is a library container named "soffice." Libraries stored in the application are globally available to all macros.
Every document is a library container.
The library named Standard is special; it always exists and cannot be overwritten. I recommend against using the Standard library.
Always give meaningful names to the libraries and modules that you create. For example, Library 1 and Module4 are not meaningful names , although AXONInvoiceForm1 might be more descriptive and helpful.