• 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.

Understanding Engages Sample Code

Messages
135
Country
us-kentucky
Recently, I was directed to Engaged's nice article on How do I share data between c-gauges in a shared cockpit scenario: Part 1.

I am having difficulty understanding one part of her sample code from that article.

In the article, she defines some function prototypes:

BOOL clock_control_button( PGAUGEHDR gauge_header);
BOOL clock_select_button( PGAUGEHDR gauge_header);
BOOL clock_toggle_temp_volts_button( PGAUGEHDR gauge_header);

one for each of the three buttons on the clock. Later in the switch statement she calls them, where their return value presumably tells if the associated button is/has been depressed.

I am confused by a lack of function definition in her code. It seems (if I grasp this) that like a typical callback, she is passing the calling gauge structure, but what would the definition of these functions look like?

To do a button, I generally have defined a local bool variable that represents the state of the button which is updated/maintained in the button's MAKE_ICON callback. I'm sure the definition probably wasn't supplied intentionally to abstract it a bit, but it has me thinking she would do something different, and I'm curious what it might be.

Anyone shed any light on this?

Patrick
 
Back
Top