<html><head></head><body><div>On Thu, 2020-12-17 at 13:49 +0000, Michael Johnson wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="auto">All those warnings are related to not handling the None type, I didn't think that would have any bearing. </div></blockquote><div><br></div><div>You were ignoring Results. set_property(), emit(), etc return Results.</div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="auto"><div dir="auto">Wait. You're not supposed to use emit? Then why does it exist? Surely you emit a signal to then be caught by the connect.</div><div dir="auto"><br>What is the alternative to using emit then, and why does the alternative still relate to connect? </div></div></blockquote><div><br></div><div>One side is connecting to a signal, the other side is emitting signals. For normal signals, the emitter is the object itself. In this case playbin.</div><div><br></div><div>For action signals (get-audio-tags on playbin for example), you would emit the signal instead of playbin. Action signals "abuse" the signal machinery for having something like "dynamic function calls".</div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="auto"><div dir="auto">By the logic of setting the value of 2 every them then current audio should go -1,-1,2 not -1,-1,-1. It yields 2 on exit. Which was my point</div></div></blockquote><div><br></div><div>You print the current value before you set it to the new one. So in the end it is 2, but you don't print it anymore.</div><div><br></div><div><span><pre>-- <br></pre><div data-evo-paragraph="" class="" style="width: 71ch;" data-evo-signature-plain-text-mode="">Sebastian Dröge, Centricular Ltd · <a href="http://www.centricular.com">https://www.centricular.com</a></div><div data-evo-paragraph="" class="" style="width: 71ch;"><br></div></span></div></body></html>