<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dcpomatic/src/lib/signal.h, branch 3052-hang</title>
<subtitle>DCP-o-matic DCP tools</subtitle>
<id>https://git.carlh.net/cgit/dcpomatic/atom?h=3052-hang</id>
<link rel='self' href='https://git.carlh.net/cgit/dcpomatic/atom?h=3052-hang'/>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/'/>
<updated>2025-06-14T21:43:13Z</updated>
<entry>
<title>Use a new UISignal which checks thread safety slightly.</title>
<updated>2025-06-14T21:43:13Z</updated>
<author>
<name>Carl Hetherington</name>
<email>cth@carlh.net</email>
</author>
<published>2025-06-11T22:27:33Z</published>
<link rel='alternate' type='text/html' href='https://git.carlh.net/cgit/dcpomatic/commit/?id=a12a943c99ba4aba122f91c93b078d2e87146b32'/>
<id>urn:sha1:a12a943c99ba4aba122f91c93b078d2e87146b32</id>
<content type='text'>
This adds a wrapper around signals2::signal which checks that emission
happens from the GUI thread, for signals whose handlers must be called
in the UI thread.  I'm not sure how helpful it really is but maybe it
catches some bad situations.
</content>
</entry>
</feed>
