Bug 163510 - QT: Sidebar / Notes pane can not be docked
Summary: QT: Sidebar / Notes pane can not be docked
Status: RESOLVED DUPLICATE of bug 64438
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: framework (show other bugs)
Version:
(earliest affected)
25.2.0.0 alpha0+
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Qt6
  Show dependency treegraph
 
Reported: 2024-10-18 11:19 UTC by Gabor Kelemen (allotropia)
Modified: 2024-10-18 11:28 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Trying to attach sidebar/notes pane to the right/bottom of the Impress window, they did not snap (65.00 KB, image/png)
2024-10-18 11:19 UTC, Gabor Kelemen (allotropia)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gabor Kelemen (allotropia) 2024-10-18 11:19:00 UTC
Created attachment 197128 [details]
Trying to attach sidebar/notes pane to the right/bottom of the Impress window, they did not snap

Split off from bug 163428:

= Can't re-attach notes pane with KDE/QT5 =
It's possible to de-attach the notes pane, becoming a separate window.
When running with GTK3 or VCL gen I can re-attach that window to the bottom or the right of the Impress window, by moving the note pane window via it's window manager header bar. At some point it suddenly snaps back into the main window, which is the expected behavior.
Unfortunately that doesn't work with KDE/QT5 on Debian-12. The notes pane window just won't snap back into the main Impress window.

This is also true for the sidebar, not just the notes pane of Impress.

Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 693b230aed7b1ca5b6f1a95ed1a76d938f5a6645
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: qt5 (cairo+xcb)
Locale: hu-HU (hu_HU.UTF-8); UI: en-US
Calc: threaded

and back to 6.4 when qt5 started to be a thing.
Comment 1 Michael Weghorn 2024-10-18 11:28:27 UTC

*** This bug has been marked as a duplicate of bug 64438 ***