This fixes #2599

[haschu]

This hides the next to the last tick, since the last tick is always shown.

Before:

After:

[coveralls]

Coverage increased (+0.007%) to 75.747% when pulling 967f4cb on haschu:fix/2599 into ecb7ce1 on chartjs:master.

[etimberg]

I feel like this might be risky. hence the failing tests. I'm not sure the right way to handle this is to always remove the 2nd last tick. I can think of scenarios where this would lead to a large gap

[haschu]

Yeah, I had the same concerns, but I didn't found a case where this would actually lead to a really large gap.
Could you post a fiddle with an example scenario maybe?

[haschu]

Okay, I see...
How about an option like showLastTick: false instead? Not really an elegant solution - but for now it would at least give users, who come across the same problem, a way to workaround.

[etimberg]

@haschu I was actually thinking about something like showLastTick: false that could apply to all scales (numerical scales have the same problem as time scales during zoom and pan). I was thinking that rather than a boolean, the option should be an enum so that we can add more options later.

[haschu]

So, If you also consider an option like that, I'd like to come up with a solution very soon, since I need a workaround for project.

Could you give a tiny example of what you were thinking exactly? There aren't any enum options so far, so we would need a global constants object, like:

lastTick: Chart.enums.lastTick.showAlways

Wouldn't a "normal" object be more consistent to the other options?:

lastTick: {
    showAlways: false,
    anotherOption: true,
}

[etimberg]

@haschu I was thinking something like the enum you suggested. I'll let other chime in and see what they prefer. @zachpanz88 @tannerlinsley @derekperkins @simonbrunel

[haschu]

Okay.
I got a working solution with a simple boolean option running, for both numerical scales and time scales.
Depending on what the others prefer, I'll do some changes and then commit it.

[ankane]

My vote would be to exclude the last tick in this situation, to keep the labels equally spaced.

Also, thanks for this awesome library!

[fulldecent]

Can you please rebase and squash?

[panzarino]

Also, could you please fix the conflicts that have to be resolved?

[haschu]

Sure! I try to fix everything over the week.

[tannerlinsley]

This would be great. Nice work!
On Tue, Jun 28, 2016 at 11:34 AM haschu [email protected] wrote:

Sure! I try to fix everything over the week.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#2600 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AFUmCR-uFn92fyXwq15HZElmvhKOp4RZks5qQVsGgaJpZM4IiMrY
.

[ianks]

@haschu this change would be amazing... any chance you are going to finish this or should i try?

[haschu]

Oh sorry, I totally forgot that issue. I'm going to fix it as soon as I got some time :-).

[krukid]

Still a problem :(

[krukid]

Tried to hide the next to the last tick with the following config:

ticks: {
  maxRotation: 0,
  callback: function(value, index, ticks) {
    if (index <= 2 || index !== ticks.length - 2) {
      return String(value);
    }
  },
},

It kinda fixed the overlapping of the last tick, but then I resized the chart back and forth and noticed other ticks get overlapped too by some 10 pixels :(

[krukid]

so what I did was change my time scale to linear scale, which works coz all my data has an equal time step, and provided a custom renderer for ticks with fixed format. no more overlaps.

[markterrill]

Hi, any movement? It's still a nasty bug that makes it look terrible!

[etimberg]

Closing as out of date