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

P3D v1 Automatic Spoiler

lionheart said:
Tom, thanks and roger that, but don't you need a 1 before the (>K:SPOILERS_ON)?
Click to expand...

No you never need to pass a value to any KeyEvents except those that end with _SET, which are expecting a value.

What would expect 0 (>K:SPOILERS_ON) to do? :eek:
 
lionheart said:
Tom, thanks and roger that, but don't you need a 1 before the (>K:SPOILERS_ON)?
Click to expand...

Actually no. In those events that represent a single action, like _ON, _OFF, _INC, etc passing a written value has no sense as the evaluation function will discard it. There are cases though where meaningful data must be passed -ie those with _SET, _SELECT and a few others described in the SDK.

Tom
 
Hi,

No, you do not need to place a value on the stack before using a K: command, unless it is a SET type command that needs it.
 
Gee, three people in a row post the same answers! How amazing!

I tend to read the full thread before replying myself... that way I don't sound like an echo... :wave:
 
Well, I always try to reply a question that contains a personal reference :)

"Tom, thanks and roger that,..etc"

Tom
 
I don't know everything about gauge codes! sigh.... I figured there was some quantum-xml-factor for mirrored universal switch-technology coding ethics for use of on/off in a 0/1 dimension where you must factor in the relationship of the speed of light versus the Earths rotation when calculating the 'on'-ness of on.


Didn't we just have a conversation of or or, or and-or, or || where or isn't or but and or or-or.?
 
You must log in or register to reply here.
Back
Top