Comments on: Nimbus UIManager UIDefaults

By: Erik L

Erik L — Sat, 06 Mar 2010 23:31:17 +0000

Has anyone figured out how to change the Fonts? I am developing on Mac java 1.6_0_17. I have tried setting the fonts for JLabel and it does nothing. I tried setting defaultfont before setting the look and feel to Nimbus and this only changed the font for one tab title.

By: Chris

Chris — Mon, 15 Feb 2010 16:47:08 +0000

Hello,

I’m having a problem similar to Kevin’s from above. I have noticed some strange behavior with MenuBar colors. I would like to have a different color for selected text.

theDefaults.put(“MenuBar:Menu[Enabled].textForeground”, Color.WHITE);
theDefaults.put(“MenuBar:Menu[Selected].textForeground”, Color.BLACK); // Doesn’t work!

It seems that if I specify the Enabled color, Nimbus will always use it. It will only use the Selected color if I don’t specify an Enabled color. I have tried using “Enabled+Selected”, but that doesn’t work either.

Any ideas on how to work around this?

Thanks.

By: Jasper Potts

Jasper Potts — Thu, 11 Feb 2010 15:44:00 +0000

You should be able to change it simply. Just need to turn off paint for background of the text field being used as a editor and maybe reducing its padding. Basically need to set 2 properties in the client properties as shown in the blogs here. Should work. Sorry don’t have time at the moment to work out exact lines of code you need.

By: Tony Lindsay

Tony Lindsay — Thu, 11 Feb 2010 15:40:17 +0000

I think Nimbus is an excellent look and feel. Overall I have been very happy with it…
However I am having one issue where I’m having trouble finding a solution.

When the focus is given to an input component (such as JTextField, JSpinner etc) a 2 pixel border is painted around the component. In most cases this is desirable as it provides a nice visual cue to the user. However, when displaying an inline editor on a JTable, this focus highlight causes the input component to be smaller. The effect is a ’squished’ input field. To compensate, I have increased the row height of the table but this causes the table to occupy much more space.

Is there a way to selectively remove the focus highlight for an input component? If not, maybe this could be added in a future release?

By: osc

osc — Tue, 02 Feb 2010 23:04:59 +0000

Have you noticed that TitledBorder draws the background color of the title over the shaded outline when TitledBorder.TOP is used? Any chance you might make the background transparent so that the outline could come through?

By: Andrew Barnham

Andrew Barnham — Tue, 19 Jan 2010 19:59:25 +0000

I had a brief look at Nimbus code from openjdk. My initial reading of it is that there is no ready way to set contentMargins based on component name and that contentMargin is a special case property. contentMargin is fixed per NimbusStyle instantiation. Maybe there is some trick I can figure out a way to instantiate a single NimbusStyle that services every instantiation of my custom “clarion” jbutton class (Nimbus.Overrides seems to instantiate a new NimbusStyle for every component which is probably at the heart of the colortree memory leak). I am also a bit pressed for time right now – but if things free up in a week or 3, then I’ll take a closer look and try to discover a good efficient workaround or patch. In meantime my workaround is – don’t use JRE u14 or above!

By: Andrew Barnham

Andrew Barnham — Tue, 19 Jan 2010 18:41:30 +0000

Thanks – greatly appreciated. This is what I have back from Sun so far.
—-
Your report has been assigned an internal review ID of 1699855, which is NOT visible on the Sun Developer Network (SDN)
—-

Let me know if you need more.

By: Jasper Potts

Jasper Potts — Tue, 19 Jan 2010 12:11:54 +0000

Looks like a nasty bug with the memory leek in ColorTree. That was not something I wrote, if you send me a bug id for the issue you filled I will try to get it looked at. I can’t remember the exact named component syntax at the moment and don’t have time to look it up. All the source for Nimbus was released into Open JDK 7 so you can grab the source there and follow though and see exactly what is supported. Sorry for making you do the leg work on this one I am just working on another deadline. Jasper

By: Andrew Barnham

Andrew Barnham — Tue, 19 Jan 2010 12:04:33 +0000

I am trying to customize contentMargins for certain buttons (not all them – otherwise buttons in forms like file dialog are affected too).

The notion of using setName() doesn’t appear to work. i.e. :
defaults.put(“Button:clarion.contentMargins”,new Insets(6,0,6,0));
defaults.put(“Button:\”clarion\”.contentMargins”,new Insets(6,0,6,0));

I found a workaround – which was to use Nimbus.Overrides client property. It worked fine until I tested it on a later version of JRE – each time i instantiate the swing component – Nimbus leaks vast amounts of memory. On a low spec machine – after user bounces in and out of about 100 windows or so (20 minutes of typical usage) – application becomes unusable. I have not pinpointed root cause – but leaky objects are all around recently added ColorTree etc. so probably started happening at u14. u10 is fine. u17 & u18 are definitely broken. Have lots of jmap histogram outputs, test code, line plots etc demonstrating this (posted on SDN – awaiting reply).

Working on a slightly unusual project whereby normal layout managers cannot be applied – and additionally I need to be able to override behaviours like contentMargin settings.

Cheers
Andrew

By: m

Fri, 04 Dec 2009 18:51:57 +0000

Okay, my background painters are working now…. but my foreground text is misbehaving. I set the following:

laf.getDefaults().put(“Button[Default+Pressed].textForeground”, Color.BLACK);
laf.getDefaults().put(“Button.textForeground”, Color.WHITE);
laf.getDefaults().put(“Button.disabledText”, Color.DARK_GRAY);

yet the result is:

Disabled JButton – foreground text is Color.WHITE
Enable unpressed JButton – foreground text is Color.WHITE
Enabled pressed JButton – foreground text is Color.WHITE

Am I overlooking something again?

Thanx, m