Posts: 4,533
Threads: 199
Joined: Mar 2006
Dean, I took a pic of this so you could see what was happening.
Before running the driver, I set verbose to Medium....but I found that I was getting no messages in the logfile.
So I created a local variable to capture the verbose setting. You see what it comes up as, but also that I have it set to medium.
Posts: 40,483
Threads: 491
Joined: Aug 2002
There are some issues with that. It definitely will reset if you set it before loading the driver or you reload the driver I think, which would require that you reset it back to what you want again.
Dean Roddey
Explorans limites defectum
Posts: 4,533
Threads: 199
Joined: Mar 2006
I closed the session, set the verbose, loaded the session...no change. So I closed the driver harness completely, started it up, set the verbose, loaded the session....still no change.
Posts: 40,483
Threads: 491
Joined: Aug 2002
Load the session, then set the verbose mode. It's definitely going to get reset currently when you load a new session. If that doesn't work, then in the meantime you might have to just put a break in the Poll() and set it there until I can get this fixed.
Dean Roddey
Explorans limites defectum
Posts: 4,533
Threads: 199
Joined: Mar 2006
I closed the harness....started it again, loaded the session, set the verbose....run and same problem. And unfortunately, I never even reach the Poll() because my error is occuring in InitSerial(). I know what the error is because I can step through it, but it took a little bit to find it.
Posts: 40,483
Threads: 491
Joined: Aug 2002
OK. I'll look into this for the next release.
Dean Roddey
Explorans limites defectum
Posts: 1,763
Threads: 76
Joined: Jun 2007
I just ran into this problem. It seems as though it is only happening in the Initialize method. In an InitializeOther() method it isn't recognizing the verbose level, but in the poll method it is.
Posts: 40,483
Threads: 491
Joined: Aug 2002
I think it is set after initialize. The thinking being that you don't really need it in initialize since that is only ever called once and so if you log some stuff there it'll never have any danger of filling up the logs. The reason for verbosity levels is because of the repetitive nature of the callbacks which would quickly fill up the logs without some sort of control.
Anyway, I'll look into this. And it will need to be available during init long run, because once I update teh driver system to allow drivers to continue to retry to initialize, then init will get called repetitively.
Dean Roddey
Explorans limites defectum
Posts: 1,763
Threads: 76
Joined: Jun 2007
I was using it here because I have a LogHandler class I use and I just plugged in my Catch routine without thinking about it. I found it interesting that you can use GetVerboseLevels().GetText() and it will give you the text from the VerboseLvls enumeration. I had never tried this with an enumeration. Normally I would have created a VerboseLvls enumeration member and set it to the GetVerboseLevels() and then extracted the value of the Text from that.
Posts: 40,483
Threads: 491
Joined: Aug 2002
Any instance of the enumerated value will give you the text values, whether it's a member or one you get back from a call.
Dean Roddey
Explorans limites defectum