Opened at 2009-07-12T20:50:15Z
Closed at 2011-05-13T23:48:58Z
#188 closed fixme (wontfix)
proper component access for time values
| Reported by: | Ichthyostega | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 1alpha |
| Component: | lumiera | Keywords: | QA |
| Sub Tickets: | Parent Tickets: | #283 |
Description
due to immediate need, Ichthyo hacked in a quick-n-dirty component access for time values (get millis, seconds, minutes, hours). This ticket is a reminder to do it properly, esp. considering overflows and rounding of negative values. Moreover, the actual implementation should be either a C function (or a real inline)
Change history (3)
comment:1 by , at 2009-10-01T23:17:01Z
| blocking: | → 283 |
|---|
comment:2 by , at 2011-05-13T23:48:58Z
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:3 by , at 2025-12-25T00:00:00Z
| blocking: | 283 |
|---|---|
| Parent Tickets: | → 283 |
Migration MasterTickets ⟼ Subtickets-plugin
Note:
See TracTickets
for help on using tickets.
Meanwhile the time handling concept is complete and mostly implemented. The basic Time entities will have no component access at all -- they are designed strictly as a one way route. The rationale is: hours, minutes, seconds is a specific timecode format. There is no point building that into the basic time value (yet there is a convenience constructor for tests). For acessing a time value in that format, quantise the time value into a definite time coordinate system and then create a timecode value based on that.