Background: VBA macro can have a defined key binding that launches the macro. We don't import that key-binding at the moment. Well actually import all the information be we unfortunately discard it. For example if we had a Macro named 'launchByKey' in and Excel spreadsheet that was bound to the key cntrl-p then this is what you would see in the VBA source code
Attribute VB_Name = "Module1"
Attribute launchByKey.VB_Description = "cntrl-p launches the macro"
Attribute launchByKey.VB_ProcData.VB_Invoke_Func = "p\n14"
As you can see the special attribute line 'Attribute lauchByKey.VB_ProcData.VB_Invoke_Func = "p\n14"' gives all the necessary info we need ( ok, we also need to recognise which procedure that attribute applies to ). Note: Currently we do at least extract information associated with one type of 'Attribute' statement see
1) legacy filter
filter/source/msfilter/svxmsbas.cxx ( SvxImportMSVBasic::extractAttribute )
2) oox filter
source/ole/vbamodule.cxx ( VbaModule::extractOleOverrideFromAttr )
In LibreOffice it is possible to provide a document only key configuration ( see the Tools|Customize|Keyboard dialog ) where a key|macro binding can be created. Finding the source code for that dialog will no doubt show how to create such a binding.
Deteted "Easyhack" from summary
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.
see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
Removing EasyHack for now as its been around since 2011-06 with little interest from newcomers so far.
Migrating Whiteboard tags to Keywords: (difficultyInteresting, skillCpp)
Hi, I'm working on this bug. I couldn't find "VbaModule::extractOleOverrideFromAttr" and "SvxImportMSVBasic::extractAttribute" functions that you said. How do you extract information about Attribute ?
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
*** Bug 118248 has been marked as a duplicate of this bug. ***