Ticket #188 (closed fixme: wontfix)
proper component access for time values
| Reported by: | ichthyo | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 1alpha |
| Component: | lumiera | Keywords: | QA |
| Cc: | Blocked By: | ||
| Blocking: | #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
comment:2 Changed 9 months ago by ichthyo
- Status changed from new to closed
- Resolution set to wontfix
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.
