Re: [Jack-Devel] Graph callback and client state

PrevNext  Index
DateTue, 09 Apr 2013 16:29:57 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToHarry van Haaren <[hidden] at gmail dot com>
Ccjack-devel <[hidden] at lists dot jackaudio dot org>
In-Reply-ToHarry van Haaren Re: [Jack-Devel] Graph callback and client state
Follow-UpHarry van Haaren Re: [Jack-Devel] Graph callback and client state
On Tue, Apr 9, 2013 at 4:27 PM, Harry van Haaren <[hidden]>wrote:

> On Tue, Apr 9, 2013 at 8:51 PM, Paul Davis <[hidden]>
> wrote:
> > there is always a race ... sometime between when you get the ports and
> when you use the information, ports could be added, removed or become
> inactive.
>
> Perhaps I'm really barking up the wrong tree, but I'm learning in the
> process here..
>
> Add the flag as described previously to JackPortFlags,
> Every time a port has its "active" flag toggled, trigger the existing
> GraphOrderCallback.
> I think this is what makes most patchbays update / redraw, hence state
> will be up to date.
>

the graph order callback only reflects changes in connectivity.

even if you use other callbacks, they arrive in specific threads, probably
not the thread that got the port info.
PrevNext  Index

1365539405.15962_0.ltw:2,a <CAFa_cKn_EBaUHp_GGVvctB4SnBjiJ-y2N7oAXBGsqgc5vY334g at mail dot gmail dot com>