that's because of threading. there is only one thread that runs the events. so it will only fire one at a time. until they are all done.
unless..... you run the
- Code: Select all
that will empty the "que" i think it just restarts the thread. never really looked into it.
funny tho your post helped me get into UDP and i designed a plugin for the xAP protocol for home automation.
someone had asked about making a plugin for xAP and since i had a little knowledge about UDP i took it on.
as far as shutting down eventghost. sure you would use the find window and then close it.
i would imagine that would work.
i know you can trigger an event in eventghost from a command line. also....
this will help you in sorting out anything you make in the future.
if you run a command prompt as admin. and go to the eventghost folder.
run eventghost with the -debug
it makes a log file in you appdata/roaming/eventghost folder
if EG hangs on startup that's ok. it found some crappy code.
go look at the log and investigate.
it will put things in there that don't even throw a traceback error. but are problems none the less