Bug 82625 - UI for inserting OLE objects on Windows is awfully confusing
Summary: UI for inserting OLE objects on Windows is awfully confusing
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Dialog OLE-Objects
  Show dependency treegraph
Reported: 2014-08-14 16:50 UTC by Michael Stahl (allotropia)
Modified: 2022-08-15 03:45 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Michael Stahl (allotropia) 2014-08-14 16:50:36 UTC
as discussed in bug 64265, the UI for inserting OLE objects
on Windows is quite bad, with 2 parallel dialog hierarchies
for inserting native Win32 OLE2 objects, and embedded objects
of formats that LO supports.

see especially comment #6 which i'll quote a bit

you can insert a native Win32 OLE object
from "Insert OLE object" dialog by 
"Create new", then click "Further objects", a dialog
"Insert Object" pops up that again has "Create new" _and_
"Create from file" options!

Apparently the "Insert OLE object" dialog is generic and available
on all platforms, while the "Insert Object" dialog uses the
"real" OLE and is only available on Windows.

i think we need both ways to do it on Windows, since you may
want to create OLE objects from files that are non-native
to LO and for which you don't have the editing application
installed... but the current UI is quite confusing.
Comment 1 QA Administrators 2015-09-04 02:48:53 UTC Comment hidden (obsolete)
Comment 2 QA Administrators 2016-09-20 10:28:32 UTC Comment hidden (obsolete)
Comment 3 Michael Stahl (allotropia) 2016-09-20 11:24:42 UTC
still confused
Comment 4 Xisco Faulí 2017-09-29 08:51:01 UTC Comment hidden (obsolete)
Comment 5 Roman Kuznetsov 2018-11-07 07:16:45 UTC
still confused (c) in LO 6.2 alpha 1
Comment 6 QA Administrators 2019-11-08 03:37:30 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2022-08-15 03:45:15 UTC
Dear Michael Stahl (CIB),

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 https://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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team