V_J wrote:It does create a folder EventGhost-xAP in my documents, and creates 3 .txt files: xAP.DebugList, xAP.EventList and xAP.IgnoreList. All files are empty.
the files will be empty until the plugin loads fully, and starts collecting data.
it's going to end up making a total of 12 files
a configuration data save file
a list of all the xAP messages (just the source class type and target)
a list of all of the events you have currently debugging
and a list of all of the events you have on ignore
and then 3 backups of each of the 4 files
it only writes data if data has changed since the last save and it rolls the backups automatically
only if the data changes will it make the backups
this is a multi step process to getting the message builder i am making set up because xap messages don't come all at the same time, they are generated as you do thing on your network and with those devices. and if someone has a bunch of devices running on xAP it's way to much data to have stored in the eventghost xml file like that.
this is all so that if you have eventghost running for a year and something happens where you lose the xml file you have a way to recover at least partial data and how you had the thing set up and the backups are for the same purpose
i is rather nice if you want to ignore say all the heartbeats and it saves it so if you restart eg they are there again yes?? or if something a week ago posted an event and you decide you want to ignore it so it's not in the eg log but it didn't save it now you have to wait and dig through the log to find that event again.
this way you won't have to do that because it has a record of it and any event that is fired from the xAP plugin will be recorded for you to ignore or to debug if you like without having to wait for the event to fire again then add it then wait again to get the debug data or to make sure the ignore worked
A loved one and Time, The 2 things that can never be replaced.
Family, The only thing you don't get to choose in life.