On 04/01/2017 01:04 PM, cecas...@aol.com wrote:
>
> Hi David,
>
> Not sure about this one. I tested some code out to see if I could figure it
> out. Had the same problem that you had with the "changed" signal not being
> blocked. If I change the rate of the file monitor and try to spool out the
Hi David,
Not sure about this one. I tested some code out to see if I could figure it
out. Had the same problem that you had with the "changed" signal not being
blocked. If I change the rate of the file monitor and try to spool out the
events, I can block the "changed" signal. Not something
On 03/30/2017 03:39 PM, David C. Rankin wrote:
> Let me know what the experts think. There is something funny about the way
> block/unblock works with GFileMonitor that I'm missing. For normal signals in
> the app, I have no problems with block/unblock.
I've posted this complete question to:
All
I have implemented a GFileMonitor/g_file_monitor_file watch for respond to
changes to the current file by an external process within an editor[1], but
now issuing g_signal_handler_block to prevent the "changed" signal from being
handled on normal saves, does not prevent the callback from
