koehil comments

Results 8 comments of


                                            koehil

StreamInfo ctor does not always return a handle on Win 64 with C#

No, it would return 2.... The main application is 15 years in development, so we are using conservative C# syntax here, but translated to (referring to the above code): `for...

StreamInfo ctor does not always return a handle on Win 64 with C#

To have more fun with threading issues, I call in the above construct: `for (int i = 0; i < 10; i++) { System.Threading.ThreadPool.QueueUserWorkItem(DoConnect); }` Now, the StreamInfos are constructed...

StreamInfo ctor does not always return a handle on Win 64 with C#

Thanks for your quick responses! In a console application I can't break the code. Not with background threads, nor with ThreadPool theads. In our Windows application however, I cannot get...

StreamInfo ctor does not always return a handle on Win 64 with C#

I've got it working! But with a very unexpected modification... It appears, that the LSLStreamInfo fails to instantiate, because the channel format specifier is not correct. I have been testing...

StreamInfo ctor does not always return a handle on Win 64 with C#

sorry, wasn't meant to close...

StreamInfo ctor does not always return a handle on Win 64 with C#

Hi, I think I have found the real problem here. There is a parameter type mismatch in the Windows API. It is the `lsl_channel_format_t`-enum type that is used as a...

StreamInfo ctor does not always return a handle on Win 64 with C#

Or keep the definition and add a new one for seemless migration...

StreamInfo ctor does not always return a handle on Win 64 with C#

Thanks for picking this up so quickly. I did find another, very old issue, that may be related, although it was about Python. I just mention it here; maybe it...