fix a problem creating and displaying connected status for ports not owned by ardour...
authorPaul Davis <paul@linuxaudiosystems.com>
Fri, 6 Sep 2013 01:39:43 +0000 (21:39 -0400)
committerPaul Davis <paul@linuxaudiosystems.com>
Fri, 6 Sep 2013 01:39:43 +0000 (21:39 -0400)
commit94efddd240f0cef752bfba5e1ccb06eb952221d1
tree6ef76faea8c524827941d3350c469591d3ef6d19
parentbc1cc154dc5b67cd49bbca87537331af3328f85b
fix a problem creating and displaying connected status for ports not owned by ardour (e.g. system:....)

This was caused by using jack_port_get_connections() which will
not return the correct status for ports owned by another JACK
client. Because of the potential for deadlock by calling
jack_port_get_all_connections(), an extra argument was added
to several PortEngine:: API calls to specify whether the call
is in a process-callback context, which defaults to true.

The only place where false is passed is within the GlobalPortMatrix
when we need to determine whether two non-ardour ports are
connected.
gtk2_ardour/global_port_matrix.cc
libs/ardour/ardour/jack_portengine.h
libs/ardour/ardour/port_engine.h
libs/ardour/jack_portengine.cc
libs/ardour/port_manager.cc