Operator Error Logging

[doug.davies]

In some of my applications, when the Preflight function finds an error, instead of opening the log window to display the error message, the error message is displayed along the bottom of the Operator window (the one with the Config, Set Config, Start, and Quit buttons). This is a problem because only the first few characters of the error message can be seen like this, so I cannot identify the configuration issues that are causing the error.
Does anyone know what would cause error messages to be written here instead of to the error log? Mostly these are errors messages that are inherited from the base class, not error messages that I defined myself.

Thanks,

Doug Davies

[griffin.milsap]

Hello Doug!

You can toggle viewing the operator log by going to View->Operator Log in the Operator.

If this doesn't bring up your log, there is one more thing to consider first. BCI2000 stores where your windows were before you quit the system last time. It is possible that you either had a different screen resolution or you simply dragged the system log offscreen and now it's rendering offscreen; just out of reach.

These settings used to be set in the registry, so resetting them in older versions of BCI2000 is not an easy task. Recently, BCI2000 has moved these settings to an "Operator.ini" file in the same directory as Operator.exe. If you're using a recent version of BCI2000 (3.0 and up, I believe), delete this file and try again -- the operator and all window positions should reset and you should be able to see them all.

-Griff

[gschalk]

Griff,

This does not seem to be the problem that he is having. From what he is saying I think he implies that the log comes up for other messages.

Any clues?

Gerv

[griffin.milsap]

Gerv,

I figured it was because he might be using several BCI2000 distributions -- a different operator and BCI2000 folder for each application. If that's not the case, I'm unable to reproduce the behavior in the current version of BCI2000.

Assuming that these problems are not errors and are instead warnings or other messages, the operator log should not change its visibility -- instead, the messages are printed to the "status bar" of the operator window (which typically isn't large enough to discern the whole warning/message) which would describe the behavior Doug is seeing.

Doug: What version of BCI2000 are you using? You can find this information by clicking Help->About in the Operator. The version number should be up at the top, and it'd also be helpful to post the compiler and build date found at the bottom (assuming a recent version of BCI2000).

-Griff

[doug.davies]

Guys, thanks so much for you response.

Deleting the Operator.ini file did seem to resolve the issue. I am running multiple versions of BCI2000 in different folders... One "vanilla" version of the executables for reference and another version of the code linked to the repository in which I am developing my application.
I am running version 3.0.2, build date July 6, 2011.
Once I deleted the file, the operator log pops up correctly, so everything is working now.