Setting a content panel removes rounded corners

[GoogleCodeExporter]

I just noticed that we are loosing the nice rounded corners when we add an 
opaque content panel to 
the CENTER position. Not sure there is a way around it. Aqua seems to simply 
switch back to 
standard cornes if the content area is completely used (see Safari). Apps like 
iTunes do not use the 
entire content area but have a bottom bar instead. In this case we can get 
rounded corners. I think 
we need a client property that controls this behaviour. I have attached a 
screenshot of my login 
dialog. The dialog uses a very light gray content panel that reaches all the 
way to the bottom. You 
can see that the dialog corners are not showing.

Original issue reported on code.google.com by dlemmermann@gmail.com on 15 Mar 2010 at 9:07

Attachments:

• corners.png

[GoogleCodeExporter]

Yes, I'm not sure what we can do here. What I'd probably do is add a 10-pixel 
high JPanel at the BOTTOM of the 
contentPane. That would probably do it.

I think we're going to have to accept that we can't just plug the Sea Glass L&F 
into an existing app and have it 
look great without a little bit of work.

I think it'll be possible eventually for the NetBeans-generated code which sets 
the content pane to work, but 
currently it doesn't.

Original comment by kahuxtable on 15 Mar 2010 at 7:26

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Didn't the newsgroup discussion lead to the proposal to remove the rounded 
corners at the bottom? Or should we use a client property on the window to 
"enable" it? (which is my preferred choice).

Original comment by dlemmermann@gmail.com on 22 Jun 2010 at 1:09

[GoogleCodeExporter]

Yes. I just haven't gotten to it yet. I'm slowly getting back into this project 
after a roughly three-month sabbatical learning to program iPhone and Android 
devices.

I'll likely get this done tomorrow.

Original comment by kahuxtable on 22 Jun 2010 at 10:10

[GoogleCodeExporter]

This issue was closed by revision r1534.

Original comment by kahuxtable on 24 Jun 2010 at 4:52

• Changed state: Fixed