Support Forum

Hello, Please provide a runnable test case not a couple of files. I don't know where to apply them to. Just zip a runnable demo and post it here. I was going throught the documentation when i came across Scalepoints and generateScalepoints which could help me but i couldn't figure out how to incorpo...

Hello, Is getBarTextRenderData currently available with the version 5.6.9? The method is there but it's private ..so I'm not sure if REACT wrapper knows of its existence (probably not). Actually I've just found out that you can use public getBarText for vertical text positioning too. For example: ge...

Hello, Yes that's possible. Yet the API is not documented at the moment and thus is considered as private. I've made a ticket to change this: https://github.com/bryntum/support/issues/9037 const histogram = new TimelineHistogram({ ... getBarTextRenderData(renderData, datum, index) { // for cases whe...

Hello, ScaleColumn is used for this out of the box. You can provide a fixed set of values: new TimelineHistogram({ scalePoints : [ { value : 5, text : '5km' }, { value : 10, text : '10km' } ], ... }); if not provided the values can be read from a record field ( scalePoints field by default) and then...

Hello, All you need to do is provide a project instance to your resource histogram project config. The histogram will calculate the data. Also i have requirement to show a value from data using getBarText in such a way that the value appears at the top of the bar. Please provide guidance on how this...

Hello, If the task's calendar and the resource's calendar do not have any overlap then show it as in case "2b". Is there a way to do this? Theoretically you can change the histogram data before rendering ( this guide has some info on that regard). So you can adjust any tick values. But I t...

Hello, You could try something like this: const histogram = new TimelineHistogram({ ... getRectClass(series, rectConfig, datum) { // If "work" value is less than "travelTime" // reorder the bars if (datum.work < datum.travelTime) { switch (series.id) { case 'travelTime': rectConf...

Hello, Is this expected behavior? If so is there a way to prevent it? Yes this is by design. Events are scheduled ASAP and start/end dates are calculated fields. So Scheduler Pro enforces event positions with a constraint. And then start/end dates are calculated. To prevent this you can: turn the ev...