30 Jan
2004
30 Jan
'04
8:32 p.m.
On Fri, Jan 30, 2004 at 07:18:02 -0500, Dave Robillard wrote:
On Fri, 2004-01-30 at 19:01, Steve Harris wrote:
Having looked at it some more I dont think it is a bug - I dont think a
client dosconnecting completely counts as deregistering.
Wether it should or not I dont know. I'm doing some more testing.
- Steve
On Fri, Jan 30, 2004 at 03:35:37 -0500, Dave
Robillard wrote:
I did notice that the graph_order_callback was being called, but the
process of trying to figure out if a port has actually disappeared (or
something has just been connected) is both really gross and really
inefficient. The Jack API documentation says
port_registration_callback is supposed
to be called on port register AND deregister, but it only seems to be
called when a port is registered.
So essentially, how can an app know when a jack port is deregistered?
Youre right, theres a bug. I'l look at fixing it.
You might try jack_set_graph_order_callback(), which will detect it often,
but not always. I wonder why noones noticed this before.