1° The title of the view is not correct.
This bug is visible in your example
docs.dhtmlx.com/scheduler/sample … _days.html
The view really shows data between 30 jun 2014 and 06 jul 2014 and the title says “30 Jun 2014 to 27 Jul 2014”.
For the title, each “section” column is a date. (4 sections * 7 days = 28 days intervals).
I try to change title with
scheduler.templates.unit_date = function (start, end) { … };
or
scheduler.templates.week_unit_date = function (start, end) { … };
or
scheduler.templates.single_unit_date = function (start, end) { … };
None of these functions is called.
scheduler.templates.week_date = function (start, end) { … };
is called, but the end date does not match the real end date
2° Unable to color the weekend
In standard views “day” and “week”, I use this to color the weekend
scheduler.templates.week_date_class = function (date, today) {
if (date.getDay() == 0 || date.getDay() == 6)
return “weekday”;
return “”;
};
It does not work in the view unit in multiday, Probably for the same reason that the point 1. each “section” column is a new date.
3° the method checkInMarkedTimespan not work with sections
I create MarkedTimeStamp like this
var options = {
start_date: …,
end_date: …,
css: “mycss”,
type: “mytimespan”,
html: …,
sections: {
doctor_5: “ABC”,
doctor_10: “ABC”
}
};
scheduler.addMarkedTimespan(options);
when i use
scheduler.checkInMarkedTimespan(scheduler.getEvent(id), “mytimespan”)
or
scheduler.checkInMarkedTimespan({
start_date: …,
end_date: …,
section_id: ‘doctor_5’
}, “mytimespan”)
checkInMarkedTimespan return always “false”
But, if I create MarkedTimeStamp like this
var options = {
start_date: …,
end_date: …,
css: “mycss”,
type: “mytimespan”,
html: …,
};
scheduler.addMarkedTimespan(options);
checkInMarkedTimespan return then good result but graphically the MarkedTimespan are not drawn by section