Issue 54125 - Table Properties Lost on Multiple Monitors
Summary: Table Properties Lost on Multiple Monitors
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOO 2.0 Beta2
Hardware: All Windows XP
: P3 Trivial (vote)
Target Milestone: AOO PleaseHelp
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2005-09-01 22:42 UTC by mudpyr8
Modified: 2017-05-20 11:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description mudpyr8 2005-09-01 22:42:18 UTC
I was running Writer on my laptop with a second monitor aligned on the
right-hand side. I worked on a document for a couple of hours with the document
displayed on the secondary monitor, saved, shutdown, and disconnected. Later I
connected to a different monitor, aligned on the left-hand side, and opened my
document. The document appeared this time on the main monitor (which is fine),
but when I went to open Table Properties for a table in the document it seemed
to freeze, and no table properties window appeared. I hit ESC and it was fine.
Selected Table Properties again and the same thing happened. Attempting
everything, I realigned my secondary monitor to the right-hand side (in Display
Properties), hit apply and blam, the table properties appeared... on the main
monitor. I realigned the secondary to the left and the properties stayed on the

Quirky behavior, and the app didn't crash, but this could possibly confuse
someone to tears.

One other factor that may be in play is I am using Virtual Dimension
( I did not test this with that software
turned off.

Thank you. The suite is awesome.
Comment 1 michael.ruess 2005-11-01 13:06:46 UTC
MRU->JW: could you please investigate this?
Comment 2 jack.warchold 2005-11-11 10:56:14 UTC
confirmed on scr680_m139 with my system Matrox G450 and dualhead enabled

reassigend to ssa

set target OOo later
Comment 3 stephan_schaefer 2005-12-05 14:06:05 UTC
ssa->hdu: the window positioning code normally checks if the coordinates are
completely out of the monitor region and should avoid placement there. may be
you should have a loki at SetWindowState() (which is used to position dialogs)
and GetDesktopRectPixel() (which returns the monitor size)
Comment 4 2005-12-20 14:53:42 UTC
Comment 5 Marcus 2017-05-20 11:29:56 UTC
Reset assigne to the default "".