Borland C++ Builder 2010

[gdimitri]

Hello everyone,

I have just started using BCI2000 and have come across some issues that you might want to know.

I have successfully compiled and used (in a simple fushion) the v3.0 of the software using VS2008 express. I also needed to have the RDAClient source module compiled but I realized the source code needs the vcl borland libraries. I had then to download a trial version of BCB2010 in order to compile the RDAClient using its .bpr file. Since I am using RDAClient to try and interface FieldtripBuffer as a data source to BCI2000 (Robert Oostenveld's implementation) I am not sure whether the BCB compiled code will work fully with the VS compiled one. Can you verify this please?

I then used BCB2010 and tried to compile the V2.0. Initially I got some errors in the ParamDisplay.cpp in the src/core/operator that had to do apparently with the Unicode support implemented in BCB2010. The line with the main error that caused all the rest is:
617: BROWSEINFO browseinfo =
with error
[BCC32 Error] ParamDisplay.cpp(679): E2015 Ambiguity between 'BROWSEINFOA' and 'Shlobj::BROWSEINFOA'

I solved that by doing this
::BROWSEINFO browseinfo =
If I did Shlobj::BROWSEINFO then I had to make buffer and mComment.c_str() into wchar_t and then BROWSEINFO became BROWSEINFOW and other parts of the code broke.

Yet although the above allowed the code to compile I can't seem to make it run. I can launch the BCI2000 launcher and after I put the required modules to their folders I launch SignalGenerator DummySignalProcessing and StimulusPresentation (as I do in V3.0 which works great) but in the operator that pops up the Config and Set Config buttons are greyed out while the status in the Launcher says:
Launching Operator...
Launching SignalGenerator
2

Also every time I close the Launcher the BCI2000Launcher.ini file clears and I have to reposition all the modules.

I thought you would like to know about these issues and I would like some help in making the BCB2010 compiled v2.0 BCI2000 work.

thank you for your time

[mellinger]

Hello,

thank you very much for reporting these issues.

I am not sure whether the BCB compiled code will work fully with the VS compiled one. Can you verify this please?

The BCI2000 protocol is independent of the compiler used to compile the modules. So mixing modules compiled with different compilers will definitely work.

Also, the protocol has not changed between v2 and v3, so mixing modules from these two versions should work as well.

Thanks for providing a suggestion how to fix the Borland compiler error.

I will look into the issues with BCI2000 launcher in v2 as well.

Regards,
Juergen

[mellinger]

The issues with BCI2000Launcher are now fixed.