https://bugs.freedesktop.org/show_bug.cgi?id=64265
Michael Stahl <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected], | |[email protected] See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=51274 Component|Writer |Installation --- Comment #4 from Michael Stahl <[email protected]> --- cannot reproduce this problem with 4.2.3.3 or master... OleComponent::LoadEmbeddedObject() just calls Win32 OleLoad(), and that's what determines which component is going to handle the OLE object, via the registry entries. OleComponent::RunObject() just calls OleRun(). there is code in setup_native/source/win32/customactions/reg4allmsdoc/reg4allmsi.cxx to create registry entries to associate Visio files with LO; presumably the problem is caused by these entries over-writing the entries that Visio itself creates. in my test i've installed Visio 2007 after installing LO, which would explain why i don't see the problem, presumably Visio will over-write all its entries. am not quite sure if it's possible to selectively disable/enable LO's registration for particular MSO document types; clearly all of it can be disabled with REGISTER_NO_MSO_TYPES... ah it checks also SELECT_WORD, SELECT_EXCEL, SELECT_POWERPOINT, SELECT_VISIO.... so i guess you can specify the SELECT_VISIO property when installing with msiexec to disable LO registration for Visio types. Andras, do we already check that we don't over-write existing entries in the registry when installing? in summary, not sure if there is a bug here at all. -- 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
