Fix tooltip error and add fixed steps to linear scale

[roben]

I noticed that using the label callbacks only added all returned contents to a single line in contrast to the documentation: "All functions must return either a string or an array of strings. Arrays of strings are treated as multiple lines of text.". This pull request fixes this.

[roben]

And sorry for the merge conflict, tried to amend after pushing.

[roben]

I have updated the pull request which now also sports a ticks.fixedStepSize option to force fixed linear scale steps instead of automatically generated ones. In my case I had to display ranking table changes over time and there were positions skipped or even half positions displayed depending on the ranking size / max value. I also fixed a typo from the broken commit earlier.

[etimberg]

@roben did the tabs / spacing change in the linear scale? It looks like the entire file changed :| It also looks like a really old version of the file. Can you also merge the latest v2.0-dev into your version.

It would also be great if you could add documentation for the new option to the markdown files in the docs folder.

[roben]

It was the most recent file from v2.0-dev but I used Netbeans' auto format which had different indentation settings than your default. I have changed and reindented it, the diff is much lighter now.
I have added the configuration documentation in a new table for the linear scale section as the parameter only applies there.

I have also added the built files to the commit just for completeness.

Note that I needed to change "gulp": "3.5.x", to "gulp": "3.9.x", in package.json to prevent gulp 3.5.6 throwing an "unsupported version" error. I did not commit that change, though, as it seems to work for your environment.

[etimberg]

Can remove this file and others in the nbproject directory

[etimberg]

@roben thanks for updated. I added a couple of comments to the diff. Once those are addressed, I'll merge this 😄

[roben]

The nbproject folder should't have been committed at all. I'll remove it.

Regarding the loop: Before implementing my changes I had issues with the graph ignoring suggestedMin and starting with 0.5 instead of 1 and I was confused by all the rounding going on there. I exit the loop after max has been reached to make sure that the last value has a tick label.

But what do you mean with

The reason is that for very small numbers this may fail.

? I can't see how this loop could fail besides looking really ugly if the step width is set too small.

[etimberg]

The case I was thinking of is when fixedStepSize is a small number between 0 and 1. It may be that the exact number is not fully representable as a floating point number. It could be that when generating the last tick, the loop bails out one iteration early. #1498 was an earlier bug where I ended up having to change the loop that generates ticks.

[roben]

I have applied the changes and merged your repository to fix the conflicts.

[etimberg]

Thanks @roben