https://bugs.freedesktop.org/show_bug.cgi?id=63846
Priority: medium
Bug ID: 63846
Assignee: libreoffice-bugs@lists.freedesktop.org
Summary: FILEOPEN: sometime import controls in xlsm document
don't fire macros
Severity: normal
Classification: Unclassified
OS: All
Reporter: nopo...@novell.com
Hardware: Other
Status: UNCONFIRMED
Version: unspecified
Component: filters and storage
Product: LibreOffice
Created attachment 78376
--> https://bugs.freedesktop.org/attachment.cgi?id=78376&action=edit
test file
Seems sometime we get a situation where an import ole control won't fire, event
bindings in vba for ole controls are dynamic, in other words the existence of
the appropriately named VBA event handler procedure is enough to ensure that
handler is associated/bound to various events of the associated control.
However to prevent 'normal' controls behaving the same way there is a mechanism
to prevent that event handling being exercised. It's controlled by the
'GenerateVbaEvents' property for each control. The GenerateVbaEvents property
is examined by the forms layer when inserting controls. However it seems that
in some cases the order in which things are called is not quite expected, e.g.
normally we would expect that all the controls are read ( and properties
including GenerateVbaEvents applied ) before the forms layer code that examines
'GenerateVbaEvents' ( see OInterfaceContainer::implInsert in
forms/source/misc/InterfaceContainer.cxx ) is called. I have come across at
least one example where this is causing problem ( see attachment )
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
