Fatal Error when using Miniature App Window (v3.0)

[chazzd13]

Greetings!

Using the latest build of v3.0, I found that enabling VisualizeApplicationWindow causes a fatal error. I was able to reproduce this in both the StimulusPresentation and CursorTask applications using default parameters.

Is this a bug, or am I perhaps doing something wrong?

Thank you for any help you can provide!

[mellinger]

Hi,

I cannot reproduce the bug here -- using MSVC-built executables under Windows XP SP3, and loading example configurations from BCI2000/parms/examples, with VisualizeApplicationWindow being enabled as the only change.
Could you report details about your configuration? What do you need to do in order to trigger the bug?

Regards,
Juergen

[chazzd13]

Thank you for the reply, Juergen.

My setup is basically the same as what you described, v3.0 rev. 2938 built with MSVC (2008 Express) on XP SP3.

I can produce the error if I use StimulusPresentation_SignalGenerator.bat, load the StimulusPresentation_SignalGenerator.prm and enable VisualizeApplicationWindow. When I click Set Config, both the full and mini application windows appear blank, then "Fatal Error ..." is displayed in the bottom left of the Operator window.

Without enabling VisualizeApplicationWindow, it runs fine. Also, performing the above steps using v2.0 works fine as well.

If you have any ideas or further questions, please do let me know.

[mellinger]

Could you provide the description of the fatal error as well? It should be in the Operator's log window.

--Juergen

[chazzd13]

Hello Juergen. The fatal error actually does not seem to show up in the Operator's log. The last message is "SignalProcessing confirmed new parameters ...". After this, all buttons in the Operator window except "Quit" are greyed out, and in the bottom right, application status is "Waiting for configuration ...".

Is there any other way to get more information out of this error?

I've also compiled and run this test on 3 different computers, (2 XP and 1 Win7) and all end up with the same error. Is there a precompiled version of 3.0 available? I could test that, if you think it'd be helpful.

[mellinger]

I sent you precompiled binaries by email.

--Juergen

[chazzd13]

Thank you so much for the binaries, Juergen. I tested them with "VisualizeApplicationWindow" enabled, and it works! I found that replacing my OperatorLib.dll with your version solves the problem. Do you have any idea about what might be causing this discrepancy in dll's produced?

[mellinger]

Maybe it is a Debug vs. Release build issue, or your DLL was outdated but had a recent file time so it was not rebuilt?

[chazzd13]

I've tried Release builds from scratch, but it still ends up with the same result. However, at least now I can use the working DLL that you sent. Thank you again for the help, and if ever you have any other ideas please do let me know.