|
Haskore.RealTime.EventList.TimeBody |
|
|
Description |
Apply actions to event lists
(starting with time, ending with body)
at given times.
|
|
Synopsis |
|
|
|
Documentation |
|
T (Cons, decons) |
|
mapBodyM |
|
mapM |
|
mapM_ |
|
getBodies |
|
mapBody |
|
mapTime |
|
mapTimeTail |
|
empty |
|
singleton |
|
null |
|
viewL |
|
viewTimeL |
|
viewBodyL |
|
cons |
|
snoc |
|
consBody |
|
consTime |
|
append |
|
concat |
|
cycle |
|
insert |
|
decreaseStart |
|
delay |
|
partition |
|
foldr |
|
slice |
|
normalize |
|
collectCoincident |
|
flatten |
|
mapCoincident |
|
resample |
|
toAbsoluteEventList |
|
|
The next set of routines is more precise.
It computes a time table starting with current system time
and tries to stick to it.
So far, I worked hard to use time differences instead of absolute times
in order to avoid increasing memory consumption of time numbers
(which however slows down as time evolves)
but the time related functions of the system are absolute,
so have to make our ones absolute as well.
|
|
|
The wait calls are necessarily quantized,
but the time passed to the action is not quantized.
|
|
|
This routine is only necessary,
because differences might be too small
to be noticed in the absolute time values.
That is, collectCoincident will split events which actually belong together.
|
|
|
|
|
The first function assumes,
that the action does not consume time
and that the wait command is precise.
It is not very useful in practice, but very simple.
|
|
|
|
attachTime :: T time body -> T time (time, body) | Source |
|
We export this function only for use in Haskore.RealTime.EventList.TimeTime.
|
|
Produced by Haddock version 2.4.2 |