• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Client Data Area and Client Event Names in SimConnect

DocMoriarty

DocMoriarty

Messages
64
Country
germany
Just a proposal for addon developers:

Client data area names and client event names are shared on the server. To avoid unnecessary confusion of multiple clients using the same names, the names should not only contain the add on name but also at least the company or author. (I don't want to know how many "FSLog" clients are out there or how many autopilots and gps gauges are in preparation)

For example:

"FSLog.MyEvent" <- bad
"MoriartyIndustries.FSLog.MyEvent" <- much better
"DE.MoriartyIndustries.FSLog.MyEvent" <- nearly perfect
"ThisUniverse.MilkyWay.SolSystem.Earth.DE.MoriartyIndustries.FSLog.MyEvent" <- as perfect as it can get

Not that my current add on is named FSLog, it's just to illustrate the problem.

Edit:

Likewise that should also be used for the client name itself of course:

"FSLog" <- bad clientname
"MoriartyIndustries.FSLog" <- much better
 
Last edited:
You must log in or register to reply here.
Back
Top