Opened 14 years ago
Last modified 14 years ago
#73 new defect
Polarbar mailer
Reported by: | BlondeGuy | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Enhanced |
Component: | general | Version: | 1.6.0-b19 RC |
Severity: | low | Keywords: | |
Cc: | neil@… |
Description
This e-mail client works under other OS/2 Java
I can start the mailer, and it works with one exception. The window where the message would display is never painted, and whatever would be behind the program window shows through.
The window, folder list, message list, etc all paint OK.
If I compose a message, the window where the message is composed also does not paint.
If I change the browser window style from text browser to ICE HTML Browser, I get the message window to paint.
Polarbar mailer is attached; use the following to invoke:
javaw -cp .;polarbar.zip org.polarbar.mailer
Change History (7)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Milestone: | → GA |
---|
comment:3 by , 14 years ago
Priority: | major → minor |
---|
Thank you for the report.
Polarbar uses AWT from what I see (i.e. not Swing). AWT is in turn a wrapper around native window classes which are in this case provided by Odin32, by emulating the respective Win32 window classes. Looks like there is some bug in this emulation (related to the scroll area).
While it would be nice to fix these bugs per se, this looks more like an Odin32 task and has not much to do with Java.
More over, PolarBar is really old and dead and bogus (and there are better alternatives) so I'm lowering the priority. So far, this is the only application that shows the repaint problem in AWT and we have more important things to do.
follow-up: 5 comment:4 by , 14 years ago
Milestone: | RC2 → GA |
---|---|
Severity: | → low |
comment:5 by , 14 years ago
Replying to dmik:
I can only say that I use Polarbar, even though I can use other mail programs. It's handling of sending to a group is really cool. If you fix the Odin problems, then great. I'll enjoy the new Java 6 port for many other reasons.
comment:6 by , 14 years ago
Thank you for your feedback. It's just the fact that our resources are limited and it seems that doing things such as fixing SMP and porting the Java browser plugin are more in-demand than fixing raw AWT (Odin) issues that don't show up in Swing and other Odin-based applications.
Attachment is too large -- get Polarbar from here:
http://www.xs4all.nl/~frobozz/polar/pbm125e.zip
Thanks.