https://bugs.documentfoundation.org/show_bug.cgi?id=150547
--- Comment #3 from Mike Kaganski <[email protected]> --- Anything can be documented. But any complaint like "your documentation is unusable" is just useless. There is a good source of information at https://wiki.documentfoundation.org/Macros. There is a new "Development Tools" feature [1] (indeed, too new for 6.4.7.2 as set in the report's metadata), that allows one to discover all the available methods of any object, including those of current document (that is represented by 'thisComponent' in Basic). There's also a Watch feature that has always been in Basic IDE, that allows you to inspect 'thisComponent', including complete type information under its 'Types' node, which is indeed not easy to scan, but contain every interface it implements, and every method it exposes; and also under its 'SupportedServiceNames', where one can see a few services, which can then be looked up in the API documentation, to have somewhat narrower understanding of what this object is. And the documentation for OpenOffice mostly is applicable (and being gradually adopted, like Developer Guide, that lately found new home in our wiki [2]). And finally, there are always ways to ask questions, as Rafael mentioned, and then take an effort to suggest own improvements to the topics that were difficult to oneself, as the contribution to the project. By the way, thisComponent (of Calc) *definitely* has Sheets property. So the problem here is something done wrong by OP in the macro, that needs discussion e.g. at Ask LibreOffice, together with the macro code itself, to figure that. Any software, no matter who and how creates its documentation, has lots of discussion everywhere over the net, e.g. on StackOverflow, because it's impossible to cover any problem of any (new or experienced) developer involving this software. [1] https://wiki.documentfoundation.org/ReleaseNotes/7.2#Core_.2F_General [2] https://wiki.documentfoundation.org/Documentation/DevGuide/LibreOffice_Developers_Guide -- You are receiving this mail because: You are the assignee for the bug.
