Issue Details (XML | Word | Printable)

Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: kirillcool
Reporter: gervaisb
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Bad comportments with dual screen

Created: 17/Sep/08 12:17 AM   Updated: 17/Sep/08 05:43 PM
Component/s: base
Affects Version/s: 4.0
Fix Version/s: milestone 1

Time Tracking:
Not Specified

File Attachments: 1. Zip Archive (688 kB) 17/Sep/08 12:25 AM - gervaisb


Operating System: Windows XP
Platform: PC

Issuezilla Id: 18
Participants: gervaisb and kirillcool

 Description  « Hide


I have jus tried the lastest release of Flamingo from Pushing Pixels
testRibbon.jnlp (September 15, 2008).
I have a dual screen configuration and when the application start i can't move
it to the second screen. After changing the look and feel ro "Windows" I can
move the frame to the second screen but when I try to expand it, she don't pick
the correct size (more width and not enough height).

I'm using the jdk_1.6.0_10. I you want I have two screenshots to explain the
problem. You can contact me at


kirillcool added a comment - 17/Sep/08 12:22 AM

Currently there is no built-in support for multi-monitor setup in Ribbon
component. How does Office 2007 behave in your setup? Can you maximize it to
both screens? What happens when two screens have different pixel dimensions?

Marking this as ENHANCEMENT for the next release with first step to understand
the required behavior of a frame with ribbon under multi-monitor environment.

gervaisb added a comment - 17/Sep/08 12:25 AM

Created an attachment (id=6)
Screen1: When the app start. Screen2: Whne i have changed the l&f to Windows to move the frame and tried to expand it.

kirillcool added a comment - 17/Sep/08 05:43 PM

Moving to version 4.0. Note that the official ribbon specification doesn't say
anything about the behavior under multiple monitor setup. I'll try playing with
Office 2007 on such a setup when i find time.

kenaiadmin made changes - 25/Jan/11 12:59 PM
Field Original Value New Value
issue.field.bugzillaimportkey 18 69682