If you get an event that is say, 5 hours, and move it, so it overlapps to the next/previous week/day and then go to the next week in the view, it looks fine, if you move the event even by one hour, the even suddenly gets bigger by several hours / days. You can keep moving it while it is spanning multiple days.
This is down to the ignore_timeline property. Without this set, our script works fine, however, we need to hide weekends and only show 12pm to 5pm, when we add the relevant script, it all breaks when you start dragging over to multiple weeks/days. Just as a note, this is replicated in your sample on your website, just get a task, drag it so it spans over the weekend, and then keep shifting it by an hour at a time, and watch it expand more and more each time.
Hi,
thanks for the problem report!
It’s a known issue, the fix will be included in the next version of the scheduler.
You can try our latest development version of the extension. dhtmlxscheduler_timeline.js_20140507.zip (11.2 KB)
Hi,
sorry for a late answer, this issue is still present, that’s right. We are working on it. We had much to do for the scheduler 4.1, but some issues escaped. We hope it will be fixed with 4.1.1 release. When the fix will be available we will post it here. Thank you for the patience.
Please include this file on the page after
“dhtmlxscheduler.js”
“dhtmlxscheduler_timeline.js”
It should fix the issue. dhtmlxscheduler_event_length_fix.js.zip (1.15 KB)
Thanks for the fix. This resolves the issue, kind of, but you might want to check this bug if you are showing more than one day. For example, I am showing 5 days, from 12pm to 5pm each say. If you put an event on the overlap between days, sometimes the start date is 12pm, sometimes it flicks to 5pm (the previous day). Then, sometimes, when dragged, it adds an hour to the length.
The start time flickering is kind of feature - if you start drag operation in last time cell of previous day - start date will be set to this time. If drag started in the first cell of new day - event will start from this date. We will improve this behavior in the next build.