https://bugs.freedesktop.org/show_bug.cgi?id=71248
--- Comment #13 from Justin L <[email protected]> --- bug (re)introduced around Nov 28, 2012 by a patch marked as date 25-Mar-2011 by Daniel Rentz @ oracle.com, comment "calcvba: #164410# improve VBA compatibility implementation in various areas:". At this time SC_UNO_VBADOCOBJ/"ThisVBADocObj" was changed to SC_UNO_VBAGLOBNAME/ "VBAGlobalConstantName". This appears to be rebasing the code on OOo. Simply replacing 'ThisVBADocObj' in objxtor.cxx to produce this line: xProps->getPropertyValue("VBAGlobalConstantName") >>= aConstName; will fix the problem. That matches the OOo code. "ThisVBADocObj" is also referenced in LO Writer (but not in OOo Writer) (sw/inc/unoprnms.hxx defines UNO_NAME_VBA_DOCOBJ as "ThisVBADocObj".) It doesn't appear that anything uses this code, so it should be safe to "tinker" with it. UNO_NAME_VBA_DOCOBJ introduced into Word around October 2010 by Noel Power, comment "initial commit for vba blob ( not including container_control stuff )" The WORD portion probably needs the same fix as happened in Bug 54721, changing sw/source/core/unocore/unomap.cxx: { OUString(UNO_NAME_VBA_DOCOBJ), WID_DOC_VBA_DOCOBJ, cppu::UnoType< cppu::UnoSequenceType<css::beans::PropertyValue> >::get(), PropertyAttribute::READONLY, 0}, to: {OUString(UNO_NAME_VBA_DOCOBJ), WID_UNO_NAME_VBA_DOCOBJ, cppu::UnoType<OUString>::get(), beans::PropertyAttribute::READONLY, 0}, and fixing UNO_NAME_VBA_DOCOBJ in sw/source/core/unocore/unomap.cxx and sw/source/uibase/uno/unotxdoc.cxx (or sw/source/core/uibase/uno/). -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
