https://bugs.documentfoundation.org/show_bug.cgi?id=101222

            Bug ID: 101222
           Summary: Writer can not be pinned in the taskbar when launched
                    by a document
           Product: LibreOffice
           Version: 5.0.6.3 release
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Hello

Under Windows 7, when I launch Writer by opening a document in the file
Explorer, the Writer icon in the taskbar can not be pinned.

Steps to reproduce:
. Ensure Writer is not open.
. Launch the Windows File Explorer.
. In the Explorer, Open a Writer document (.odt).
. Once Writer is launched, right-click on its icon in the Windows taskbar.
. Note the menu has not the usual option "Pin this program to the taskbar".


As a developer, I suspect this is due to the fact the process that really
displays the document is "soffice.bin", not a classic ".exe" file name
(although it is an executable).


Suggestion to the developers:

1. Remove the unusual executable launch chain: swriter.exe, soffice.exe,
soffice.bin .
2. Transform soffice.bin to a dynamic library: soffice.dll (in Windows, or
equivalent on others OS).
3. Link soffice.dll to switer.exe, scalc.exe, sdraw.exe, etc.

This way, swriter.exe is the real process that displays the document. And only
one process is launched (more clear, less resources, faster to run).

That will prevent all bugs that are linked to the current executable launch
chain.
For example the bug #76131, I presume.

Thank you

P.S.
Please note Writer can be pinned to the taskbar when launched as an
application, and not launched by a document.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to