Bug 47501 - Sheet tab context menu don't show in second monitor UI
Summary: Sheet tab context menu don't show in second monitor UI
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.5.1 release
Hardware: x86-64 (AMD64) macOS (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 51445 54983 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-03-19 04:54 UTC by Javier
Modified: 2013-01-28 11:10 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Javier 2012-03-19 04:54:37 UTC 
I have two monitors attached to my computer, the first one at 1920x1200 and the other at 1400x1050 of screen resolution.

When I have the Spreadsheet application maximixed in the lower resolution monitor and try to show the popup context menu in the sheet tab (mainly for delete sheets) it doesn't show. I only get a empty oneline menu popup. Manipulating this oneline entry I can manage to reveal all menu entries.

If the application is not maximixed or is maximixed in the main full resolution screen, no problem occurs. So I guess the app mismatch the screen space avalible to show the context menu.

This only happens to me in the sheet tab, other context menú (for cells, rows, toolbars, ...) work fine

Thanks
Comment 1 bfoman (inactive) 2012-08-10 13:20:33 UTC 
Checked with:
LO 3.5.5.3 
Build ID: own W7 debug build
Windows 7 Professional SP1 64 bit

Monitor 1: 1680x1050
Monitor 2: 1024x768

Could not reproduce.
Comment 2 bfoman (inactive) 2012-09-20 17:02:27 UTC 
*** Bug 54983 has been marked as a duplicate of this bug. ***
Comment 3 Uwe Altmann 2012-10-10 18:36:30 UTC 
Checked with 
LO 3.6.2., Mac OS 10.6.8
1440x900 and 1680x1050 Monitor set. 

Could not reproduce.

Do not hesitate to reopen in case of mistriage.
Comment 4 bfoman (inactive) 2013-01-28 11:10:08 UTC 
*** Bug 51445 has been marked as a duplicate of this bug. ***