-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Description
Partially verified Testathon 2025-12-16
Static ticks are a problem
This approach now uses a static 10 ticks per plot. This will cause regression issues when plots are small in a view:
Additionally, even in larger views the ticks are colliding in some cases. I see this mostly when changing the timeframe in the Time Conductor:
Proposal for solution: Dynamically determine a number of ticks that can be displayed in the available pixel space based on the tick size and adjust the number of ticks accordingly.
Ticks sometimes display the date and sometimes just the time
In timeframes where all ticks are within the same date (i.e. a date boundary is not in view), the view will display ticks with just the time. As soon as the ticks span two different dates, then all ticks get the date and time. This has a couple undesirable effects:
* When only the times are shown, the user has no context of the date. * It's hard for the user to understand the model.* Always apply the date with the time in the first tick in view (blue arrow). * If a date boundary is in view, apply the date to the first tick in that date only (orange arrow). This acts as a clear demarcation of the date boundary and supplies the date context to the user.@charlesh88
Dynamically generating ticks is more involved and will require significant testing. I've reverted the # of ticks to 6 like they used to be before.
I've moved this out as an enhancement - I'll have this for testing soon.
Originally posted by @shefalijoshi in #977


