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

V Stuart Foote <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=15
                   |                            |0236
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
            Summary|LibreOffice does not        |Incorrect handling of
                   |remember the window         |FullScreen mode (Writer and
                   |position in fullscreen with |Calc) parsing
                   |more than one Screen        |ooSetupFactoryWindowAttribu
                   |                            |tes, LO module jumps to 0,0
                   |                            |position on relaunch
                 CC|                            |[email protected],
                   |                            |[email protected]

--- Comment #1 from V Stuart Foote <[email protected]> ---
Confirmed, manifests in the user profile .XCU for the
ooSetupFactoryWindowAttributes where direct closing (<Ctrl>+Q) a module placed
in FullScreen mode (<Ctrl>+<Shift>+J for swriter.exe or scalc.exe) appends a
mode "68" to the xy positions of the window in the .XCU setup.

mode "1" is standard sized window
mode "4" is Maximized sized window

I don't think mode "68" is being parsed correctly (but is applied for both
Writer and Calc sessions so not spurious), and on relaunch of the module the
fallback is to mode "4" with positioning from 0,0 window reference.

It is more noticeable with a multi-head system, but the mode "68" --> "4"
affects single screen as well (just not as obvious).

Believe this comes from the refactoring of the mbFullScreen in
https://gerrit.libreoffice.org/c/core/+/135809 and friends.

Related for 7.4 in see-also bug 150236, but this remains for 7.5 and trunk
against 7.6

@Jan-Marek, could you have a look.

=-testing-=

Build ID: 74dc2ac66f0130bcd77cf1bbe417b22865beb067
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

Screen1 is 1920x1080
Screen2 is 1920x1080

=-taken from .xcu at different steps-=

xcu after LO swriter.exe launch on screen1 and drag to screen2, swriter
Maximized and doccument save
<item
oor:path="/org.openoffice.Setup/Office/Factories/org.openoffice.Setup:Factory['com.sun.star.text.TextDocument']"><prop
oor:name="ooSetupFactoryWindowAttributes"
oor:op="fuse"><value>1920,29,1920,1051;4;,,,;</value></prop></item>

Other modules pick up x-positions on the screen2, i.e. > 1920

xcu after <Ctrl>+Q close from swriter.exe Writer in FullScreen
(<Ctrl>+<Shift>+J) mode on screen2
<item
oor:path="/org.openoffice.Setup/Office/Factories/org.openoffice.Setup:Factory['com.sun.star.text.TextDocument']"><prop
oor:name="ooSetupFactoryWindowAttributes"
oor:op="fuse"><value>1924,4,1912,1072;68;,,,;</value></prop></item>

xcu with launch of swriter.exe following close from FullScreen, opens to
screen1 in Maximized mode
<item
oor:path="/org.openoffice.Setup/Office/Factories/org.openoffice.Setup:Factory['com.sun.star.text.TextDocument']"><prop
oor:name="ooSetupFactoryWindowAttributes"
oor:op="fuse"><value>0,29,1920,1051;4;,,,;</value></prop></item>


same "68" mode for an scalc.exe launch from screen2 start, and Calc in
FullScreen mode, then <Ctrl>+Q close
<item
oor:path="/org.openoffice.Setup/Office/Factories/org.openoffice.Setup:Factory['com.sun.star.sheet.SpreadsheetDocument']"><prop
oor:name="ooSetupFactoryWindowAttributes"
oor:op="fuse"><value>1924,4,1912,1072;68;,,,;</value></prop></item>

xcu with launch of scalc.exe following close from FullScreen, opens to screen1
in Maimized mode
<item
oor:path="/org.openoffice.Setup/Office/Factories/org.openoffice.Setup:Factory['com.sun.star.sheet.SpreadsheetDocument']"><prop
oor:name="ooSetupFactoryWindowAttributes"
oor:op="fuse"><value>0,29,1920,1051;4;,,,;</value></prop></item>

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to