Hi, we just discovered an issue regarding our timeline and the hour resolution view that we had missed.
The natural thing for users when they enter a calendar item is to say "0700 - 0900" for example. In our app that is they do, and what we sthen tore as intime-outtime in the database. (mariadb datetime values).
Your calendar showcases also work like that, you specify 0900-0930 and thats how they show up. (for example https://smartclient.com/smartgwt/sho...endar_category)
--
However, if you instead show the items in a timeline, and have hours granularity, an item between 0900-1000 crosses two cells, all the way to 11.00.
I suppose it's because 11.00 is technically between 10.00 and 11.00 so also the next hour becomes busy. It is also, i guess why your timeline showcase, in contrast, display as 10.00 - 10.59. (https://smartclient.com/smartgwt/sho...ine_resolution)
This is rather unfortunate for us. is there anything that can be done about this? like some setting on the timeline "zeroValueDoesntCrossBoundary()" or something? :)
Thoughts appreciated.
The natural thing for users when they enter a calendar item is to say "0700 - 0900" for example. In our app that is they do, and what we sthen tore as intime-outtime in the database. (mariadb datetime values).
Your calendar showcases also work like that, you specify 0900-0930 and thats how they show up. (for example https://smartclient.com/smartgwt/sho...endar_category)
--
However, if you instead show the items in a timeline, and have hours granularity, an item between 0900-1000 crosses two cells, all the way to 11.00.
I suppose it's because 11.00 is technically between 10.00 and 11.00 so also the next hour becomes busy. It is also, i guess why your timeline showcase, in contrast, display as 10.00 - 10.59. (https://smartclient.com/smartgwt/sho...ine_resolution)
This is rather unfortunate for us. is there anything that can be done about this? like some setting on the timeline "zeroValueDoesntCrossBoundary()" or something? :)
Thoughts appreciated.
Comment