Monday, January 2, 2012

SteelSeries 3.9.10 (QuickRelease)

Happy new year everybody...

UPDATE: due to some minor modifications the current version is 3.9.12

I know i said it would take some months until you will see the next release but i needed some components be part of the library so i decided this morning to make a quick release and added these new things to the lib.
The new things i have added are the traffic light and light bulb you might know already from the friday fun components, another traffic light component that might fit better to different color schemes and at least 8 new indicator symbols in the IndicatorGauge. 
To give you an idea on what the stuff looks they are...

The traffic lights and the light bulb...

and the eight new symbols which are just arrows pointing to different directions...

And that's all for this i said a quick release with just a few new additions. You will find the new version either here on this blog on the right side or at MavenCentral.

For those of you that are interested in the progress of the SteelSeriesFX i could show you one screenshot of the current state...

As you can see i made some progress but it's still a looooooong way to go...

so stay tuned and keep coding...


  1. Hello,

    I found problem in release 3.9.10 for "Linear" component. I got exception for creating this component:

    Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
    at eu.hansolo.steelseries.gauges.AbstractLinear.getMinimumSize(
    at java.awt.Component.preferredSize(
    at java.awt.Container.preferredSize(
    at java.awt.Container.getPreferredSize(
    at javax.swing.JComponent.getPreferredSize(
    at eu.hansolo.steelseries.gauges.AbstractLinear.(
    at eu.hansolo.steelseries.gauges.Linear.(
    at net.cpce.netrad.client.swing.Test.(
    at net.cpce.netrad.client.swing.Test$
    at java.awt.event.InvocationEvent.dispatch(
    at java.awt.EventQueue.dispatchEventImpl(
    at java.awt.EventQueue.access$000(
    at java.awt.EventQueue$
    at java.awt.EventQueue$
    at Method)
    at java.awt.EventQueue.dispatchEvent(
    at java.awt.EventDispatchThread.pumpOneEventForFilters(
    at java.awt.EventDispatchThread.pumpEventsForFilter(
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(
    at java.awt.EventDispatchThread.pumpEvents(
    at java.awt.EventDispatchThread.pumpEvents(

    Best regards,


  2. Hi Michal,
    thx for the info, please try the latest version 3.9.12 (from this page) but be careful, it's still warm... ;)

  3. Hi Gerrit,
    thanks for quick fix. I found another problem with this component. Unit string for this component with vertical orientation is not visible(is hidden behind the LCD). I send you email with screenshot. Is possible change position of this string(e.g. somewhere near 'title' string or LED)? Thanks for reply. Regards,

  4. Hi Gerrit,

    Luckily I stumbled on your SteelSeries using a Google search. I badly need quite a number of sailing performance gauges and I was happy to see your relative windmeter (amongst others).
    So I happily replaced all my handcrafted gauges with yours and it looked fantastic (as expected). The only problem is: the performance and resource usage really suck. Are there any tips you could give to optimize performance on your gauge set?
    Do you expect the upcoming javaFX based lib to perform better (should I wait for that?)?



    Note: the worst of the pack is the Sparkline, which brings the system to a crawl quite rapidly

  5. Hi Paul,
    it depends on how you use the gauges. If you use them to visualize realtime data you should always use the setValue() methods instead of setValueAnimated(). It would be great if you could give me access to your code so that we could collaborate to get things running for you.
    You could contact me at han dot solo dot gg at googlemail dot com ... :)
    Cheers and thanx for the info,


  6. Hi Paul,

    did you consider trakStop values >(>) 100?

    how can I do this?