Closed GoogleCodeExporter closed 9 years ago
Wasnt this already reported?
http://code.google.com/p/wmii/issues/detail?id=5&can=1&q=swing
or is that one different?
Original comment by adkilgore
on 30 Mar 2009 at 7:03
No I think it is releated to that one, but I did only search in "Open Issues"
for
swing or java and didnt find a matching bug. I thought the other one was
reported in
a different bugtracker. I dont consider using open jdk a solution, neither
forcing a
special style for java applications. It works with other window managers
(although
you sometimes have to use the wmname "LG3D" hack), so this is should be
something
that has to fixed in wmii...
Original comment by que...@gmail.com
on 30 Mar 2009 at 7:34
It is the same bug. Just because it works in other window managers, it doesn't
mean
that the fault lies with wmii. There are no less than 14 ways to do any single
thing
in X11, and apps that assume certain unspecified behaviors are often burned. For
instance, many windows assume that they'll be opened with their requested size,
and
draw their contents to that size until they're resized by the user (which turns
out
usually to be a race condition).
As for Java's problem, I have no idea of the cause, but wmii has no say in how
windows draw their contents; it doesn't even give them any hints on the matter.
And,
unfortunately, Java code tends to be painfully verbose, complex, and
bureaucratic,
which means that I, personally, don't have the time to dig through its
thousands of
lines of code to find some hint of the cause.
The "solution" doesn't force a special style on the app, just a special
rendering
toolkit. The appearance is the same. OpenJDK is the same as Sun's JDK, sans some
proprietary components. Most distros should be using it by default in the near
future. I do think this should be fixed, but given that I have no clues as to
the
cause, and suspect that it's a Java issue, I can't see it being resolved any
time soon.
Original comment by maglion...@gmail.com
on 30 Mar 2009 at 7:50
Original comment by sun...@gmail.com
on 23 Apr 2009 at 5:53
Original issue reported on code.google.com by
que...@gmail.com
on 30 Mar 2009 at 6:37Attachments: