MobiFlight Community Support

Hello,

I'm learning everything about SimConnect and WASM, and write my own "connector" (reason is that I don't use Arduino, but PIC-microcontroller based HW). The source-code on https://github.com/MobiFlight is a great source to learn.

I am using VS2019 and am able to build the "MobiFlight-Connector" solution completely. I can run it from my VS2019 environment allowing me to set breakpoints and study the code.

But I have a problem with the "MobiFlight-WASM-Module". I get errors like the below.

For example, all my "std::string" are underlined, and if I hover over them, I get below error (no clue how to upload a screenshot ):

Code:

{} namespace std
no instance of constructor "std::__2::basic_string<_CharT, _Traits, _Allocator>::basic_string [with _CharT=char, _Traits=std::__2::char_traits<char>,_Allocator=std::__2:allocator<char>]" matches the argument list
      argument types are: (const char *)

Any ideas?

PS. Can I upload images in this forum? Pressing the "Image" button does give me the "img" tags, but no clue what I should put between them?

Ok, update on my previous question.

If I scrolled down in the long error list, I found something related to the "Post-Build Event". The Command Line contains the below:

Code:

mkdir "$(SolutionDir)..\..\PackageSources\modules"
copy /Y "$(TargetPath)" "$(SolutionDir)..\..\PackageSources\modules"
copy /Y "$(TargetDir)events*.txt" "$(SolutionDir)..\..\PackageSources\modules"

Because I had issues with "Post-Build Event" before, I removed this Command Line completely. And now the code is building without errors. But I still see the same errors as above (underlined curly lines), but looks like they don't have effect? Weird!

I posted my question on StackOverflow as well (https://stackoverflow.com/questions/70493574/stdstring-gives-errors-in-vs2019), and there I got the answer that Intellisense can sometimes get confused, and I should ignore the error if build is successful. So there seems no problem.

I build the DEBUG version of "StandaloneModule.wasm" and copied it in the Community folder, and it works perfectly as far as I can see. Now I can follow the traces to the Console window, and even add some more to allow me to analyze the code.

Great stuff!!!