Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    timeline error with different isc.Time.setDefaultDisplayTimezone

    Hi!

    I’ve encountered an issue when trying to display events in the Timeline component.

    I’m using a calendar where everything displays correctly. However, after integrating the Timeline into my project, I noticed the following issue:
    When I use isc.Time.setDefaultDisplayTimezone('+00:00'), the times in the Calendar adjust as expected and display correctly.
    But in the Timeline, while the time shown in the event descriptions updates, the actual elements do not shift on the timeline - they stay in the same time slots, visually out of sync.

    Am I doing something wrong, or is this a known issue with the Timeline component?

    I’m using this with a DataSource, but I also reproduced the issue in the latest Showcase build. You can see the same behavior in the Timeline Resolution example (using version 15.0d, built 2025-04-08).

    https://smartclient.com/smartclient-...lineResolution

    If you apply isc.Time.setDefaultDisplayTimezone('+00:00') either in the example file or directly in the console and then create a new event, the time shown in the event updates, but it still appears in the same (incorrect) place on the timeline.

    In contrast, doing the same in a Calendar example results in the events visually shifting to the correct time slot.

    I’ve also attached GIFs to better illustrate what I’m seeing.


    Thanks in advance for your help!


    Click image for larger version

Name:	timeline_error.gif
Views:	16
Size:	357.3 KB
ID:	275539Click image for larger version

Name:	calendar_is_correct.gif
Views:	15
Size:	506.6 KB
ID:	275535Click image for larger version

Name:	timeline_error_displaytimezone.gif
Views:	16
Size:	393.0 KB
ID:	275536

    Attached Files

    #2
    Thanks for the report - just for clarity, setDefaultDisplayTimezone() would need to be called before your Calendar was created for this to work, rather than in the browser console later.

    However, we do see the issue you describe in Timelines - we'll take a look and update here when we have more information.

    Comment


      #3
      You should find this issue fixed in tomorrow's builds, dated April 14 and later.

      Comment

      Working...
      X