I've noticed what looks like strange behaviour with the Scheduler Pro when we use the double click event to add a new event.
scheduleDblClick({ date }) {
console.log(date);
// Hide Bryntum built-in contextmenu (schedule double click)
return false;
},
The date parameter that is returned will usually be in GMT at various viewPreset modes e.g. dayAndWeek but when we change the viewPreset mode to monthAndYear the date is returning the date offset by 1 hour (GMT + 1 , BST).
e.g.
dayAndWeek
date = "2023-01-27T00:00:00.000Z"
Wed Jan 25 2023 00:00:00 GMT+0000 (Greenwich Mean Time)
25/01/2023, 00:00:00 with toLocaleString()
monthAndYear
date = "2023-01-27T23:00:00.000Z"
Wed Oct 12 2022 00:00:00 GMT+0100 (British Summer Time)
25/01/2023, 00:00:00 with toLocaleString()
Note: I'm in the UK so the local time is GMT at the moment, so I don't know where it's getting the BST value from
I have tried to reproduce this with a standalone app but it doesn't seem to do this in that app, it always returns the date correctly in GMT.
Is there a setting I can use to ensure that dates are always set to the correct timezone for each view preset?
Thanks,
Jason