On Thursday 18 May 2006 23:27, David Akbari wrote:

> One thing, as a user that I'd really like to see is the addition of 
> f-type signals as input and outputs to the UDO mechanism.

Although you cannot pass f-signals directly as UDO arguments yet, it
is already possible to copy them - with some limitations - using stack
opcodes. The limitations are: there are separate opcodes (push_f and
pop_f) for f-signals that can push or pop one 'f' variable at once,
and it is only the memory address of the variable that is pushed,
rather than the actual PVS frame data, meaning that you should pop
the signal as soon as possible, before it is changed or the instrument
instance that owns the source f-signal is terminated.