Hi Dan,

  thank you for filing the bug. I found your posts
  on various forums when researching for bug 6599351.

Dan Munckton wrote:
am I right that your are going to fix our code so it correctly handled situation when Xinerama is loaded but we have just one screen, so we could use Xrandr extension in such configuration?

Yes. I'm happy to try and produce a patch if there's no-one else working
on this issue. My employer's product will soon be directly affected by
the problem so I'm very motivated to see it solved as soon as possible.

  BTW, someone posted a hackish work around for this issue
  (see 6636469).

This would be my first contribution to Java/OpenJDK and therefore I may
not progress as quickly as others who are already involved. Is it true
that new contributors are assigned a mentor to assist a little?

This code is somewhere on boundary of AWT and 2D areas so you may want to also check with 2D. As for AWT side I can say for sure that we do not work on similar issue.

Hello 2d-dev, is there anyone aware of/working on this problem already?
(http://mail.openjdk.java.net/pipermail/awt-dev/2007-November/000109.html)

 > I've still not opened a bug on the Java bug database, do I need to do
 > that to be tidy?

you are supposed to send a path with bug id, so it looks reasonable to have one :)

I have now opened a bug which has been assigned an id. It's not yet
visible in the external database but here's the link anyway:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6636469

  As I mentioned in my evaluation (you should see it shortly *)
  this bug is related to this one:
     http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6599351

  I think this should be addressed by two fixes:
    1. we need to correctly detect whether Xinerama is present and
       active (6599351)
    2. as you suggested we should relax the requirement concerning
       xinerama and randr (6636469)

  The first part (arguably =) belongs to AWT and will need to work
  correctly on both linux ans solaris (with newer Xorg servers).

  The second part belongs to 2D. I guess for the sake of simplicity
  we could fold both issues into the same bug report since they both
  have same underlying cause.
  Typically we close the newer bug as a duplicate of the older one.
  What do you think?

  Thanks,
    Dmitri
  Java2D Team

  *) You can sign up for Java2D related bug updates, that way you
     will see the new bug reports and updates as they come in:
       http://mail.openjdk.java.net/mailman/listinfo/2d-bugupdates

Reply via email to