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

V Stuart Foote <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |NEW
             Blocks|                            |103157
     Ever confirmed|0                           |1
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=16
                   |                            |4337,
                   |                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=66
                   |                            |864,
                   |                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=91
                   |                            |282
         Resolution|DUPLICATE                   |---
                 CC|                            |[email protected]
                   |                            |om, [email protected],
                   |                            |[email protected],
                   |                            |[email protected]

--- Comment #2 from V Stuart Foote <[email protected]> ---
Actually think this would be a dupe of Patrick's bug 164337, but not the
earlier bug 66864 nor the related bug 91282 where the FullScreen Toolbar has
been docked.

And yes something is dodgy, the 'fullscreentoolbar' position will migrate to
top left corner of the active display. 

Look for it there. And if on multi-display system check the other display.

Cycling between FullScreen and diminutive LO AppFrame window (either
<Ctrl>+<Shift>+J which is a toggle, or by <Esc> simply drops back to AppFrame),
reentering FullScreen the associated Toolbar *does* always appear.

However, what seems off is that the new 'fullscreenbar' position (nPos) which
is written into the user profile, registrymodifications.xcu will be recorded as
negative (-x,-y).

In the .xcu, it starts at 30,30 on initial launch of FullScreen mode. Goes to
-5,-5 on reopen of LO, and then way off with -1386,-471--so appearing missing?

Is something set dirty and so miscalculating the nPos when the toolbar object
is again dispatched for FullScreen mode [1] rather than honoring the current
entry in profile?

=-ref-=

[1]
https://opengrok.libreoffice.org/xref/core/sfx2/source/control/dispatch.cxx?a=true&r=39bd06ad1e404b37eb70b58ee76fc52184dd4b21&h=1211#1211

=-testing-=

Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 3ab82581e5a5abc03c7ff06eac76a0b2fa0c9c34
CPU threads: 28; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan;
VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

Version: 25.2.3.2 (X86_64) / LibreOffice Community
Build ID: bbb074479178df812d175f709636b368952c2ce3
CPU threads: 28; OS: Windows 11 X86_64 (10.0 build 26100); UI render:
Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103157
[Bug 103157] [META] Full screen mode bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to