www.jfree.org

It seems there is a link missing here. You see, in category chart you (should) have value in each category for each series. Like if you think of temperature in different cities (temperature being the series, cities the category). If you have the diagonal dataset, you'll get those empty spaces for mi...

Ok, let's see if we can get this right: If data is like this you will get 4 bars in 4 categories (4*4 bars). item1 item2 item3 item4 series1 1 1 1 1 series2 2 2 2 2 series3 3 3 3 3 series4 4 4 4 4 item1 item2 item3 item4 series1 1 2 3 4 This gives you 1 bar in 4 categories item1 series1 1 series2 1 ...

So is the order of bars or the width of bars the issue?

Your latest screenshot showed that the bars got thicker when you applied Is this not what was wanted?

I ran into this myself. Try describing your data as a table, and work yourself forward from there. I quess those are all different things, so you want different colors? This is what I guess you have going on (I fell here too): Data is like this: item1 item2 item3 item4 series1 1 series2 2 series3 3 ...

Yeah I totally agree with you. I did not go all the way with my analysis, but in our case (might be other issues as you said) it was improving the situation. Back then I concluded that this was due to creating new buffered images (happened a lot for a lot of charts). But it was really tricky to have...

I disagree. Or more like I do not agree completely. Component is bad, JComponent is more acceptable. LayoutManagers are able to simplify the process as any swing developer would agree. As Richard pointed out, using BorderLayout for charting is intuitive. As I stated, using OverlayLayout on data area...

Oh, I must have misread it then..

I recall I was reading xyplot markers, but I guess those are different things.

But issue still exists, it is rendering without clearing background. This is row 693 in date axis. (call for drawrotatedstring).

When rendering labels on axis I get pretty often labels that overlay one another. This is pretty bad, since it's relatively easy to fix. You can either: 1) (HARD) have list of boxes (of taken items) and refuse to render on top of another. 2) (EASY) not fix the issue, but fix the visuals. Render with...

I'm not saying jfc should use gridbaglayout, far from it. LayoutManager2 interface is pretty simple to implement, and it allows to create ChartLayout or what ever is required, but separation of layout/renderer would *allow* the use of other *standard* methods for layouting. It's not to say that thin...

I've done some animal testing with different buffering strategies and best results were (performance wise) by buffering entire screen full, and sharing that across charts. This allowed chart resizes to be as small as possible. I've since given up on that based on the memory consumption. But it was b...

True, I used buffered charts, never saw much sense in the non-buffered.

I'd guess it's in your code. Can you shed little more light into the matter?

Yeah I got it fixed without changes to the timeline, turned out it was totally my bad.

I'll be putting this out tomorrow, I'd think there is general interest in this kind of thing.

The thing here is that the xor rendering is SLOW. It breaks the acceleration in windows machines (in my experience at least). I've got my own zooming rendering, semi-transparent rectangle without any XORring. It's working perfectly without a hitch with the acceleration. Dropping acceleration is not ...

Hi, We've produced a working hours timeline that greatly exceeds the SegmentedTimeline in capability. Basically they work the same, this is just way faster and better. I've been thinking of bringing this 'gem' to the community, mostly because there is a big issue with dateaxis (and others). The way ...