"You cannot watch a remote computer that does not have Windows NT or Windows 2000. You cannot watch a remote Windows NT 4.0 computer from a Windows NT 4.0 computer."
this is homophobia. love is love, let the NT4 computers watch each other
"You cannot watch a remote computer that does not have Windows NT or Windows 2000. You cannot watch a remote Windows NT 4.0 computer from a Windows NT 4.0 computer."
this is homophobia. love is love, let the NT4 computers watch each other
eww. the .net way to watch a file for changes is to put a FileSystemWatcher on the whole directory and set a filter glob that only matches the one file?
I mean, I guess it works, but it's an ugly API
this api has Filter, Filters, NotifyFilter, and NotifyFilters.
These are all different things.
I thought this would be an easy hack but on my first try it broke in two separate ways, and both of them are race conditions!
new race condition: I'm opening a message box every 1000ms, because the code won't disable the timer until I click OK on the message box.
ugh. I don't know why this isn't working.
I've got a filesystem watcher that triggers an event, which does fire. the event function just turns on a timer.
the timer is set to go off every 1000 ms, and it's set to call an on-timer function.
on-timer is never getting called now, and I have no idea why. It was getting called before, when it spammed messageboxes
apparently you can't enable a timer from a different thread, and guess where filesystem watcher events run?
@gsuberland yep, that was it.
@foone oh, WinForms? you need to use Invoke to modify control properties from the form's thread.
invoking it fixes it. Cool.
076萌SNS is a social network, courtesy of 076. It runs on GNU social, version 2.0.2-beta0, available under the GNU Affero General Public License.
All 076萌SNS content and data are available under the Creative Commons Attribution 3.0 license.