Chris Kleeschulte a7444a92b9 Tx event firing ... - The ProcessMessages signal was scheduling/connecting its slots slightly out of order for what we need - First, the scan_messages needs to run and copy out the stream - Second, Bitcoin's ProcessMessages needs to run in order to run AcceptToMemoryPool - Third, scan_messages_after needs to run in order to signal our tx_monitor - In order to make this happen, we need to pair ProcessMessages slot to the scan_messages slot and order that - Then, AFTER those two complete, we can schedule scan_messages_after		2015-09-23 13:05:52 -04:00
..
bitcoin.patch	Tx event firing	2015-09-23 13:05:52 -04:00