Custom events again....

[taguilo]

Multiply that by around 100 switches, lights and knobs... and it's a really, really bad idea when it comes to multiplayer/shared cockpit.

Ed,
10,100...1000...up to trigger_key_event(iEvent,iValue) is the same code, no extra lines needed. The only part that could become "heavy" is this one:

const int AC_SWITCH  = 70000;

void FSAPI EventHandler(ID32 event, UINT32 evdata, PVOID userdata)
{
     switch(event)
    {
         case AC_SWITCH:
etc

but that would be the same when using this method and by <EventID> as well.
In any case, the bad idea would be so many switches,lights and knobs and not the code to handle them

Tom

 

[WarpD]

Correct me if I'm wrong... but don't Lvars get 'broadcast' during multiplayer mode?

 

[sparouty]

Correct me if I'm wrong... but don't Lvars get 'broadcast' during multiplayer mode?

Hi,
For what I had tested during my Etendard project, L:vars are not shared between multiplayers but L:vars are shared between shared cockpit players...

Times ago, there was a thread speaking about gauge flooding, and many interesting things were said about that... I didn't find out the link...

I found also this thread that says that Custom Event can be fired with an (>K:XXXXX) call:
[FSXA] Custom EventIDs - Questions!

I didn't have time to try it but I will soon...
Regards,

Sylvain

 

[taguilo]

Correct me if I'm wrong... but don't Lvars get 'broadcast' during multiplayer mode?

Yes, that's what the SDK says (and I know of your devotion to the SDK )
However, in a C++ gaugeset scenario, only those LVars used within the model would be broadcasted and hypotetically received by nobody, so I can't see a big tradeoff here.

I found also this thread that says that Custom Event can be fired with an (>K:XXXXX) call:
[FSXA] Custom EventIDs - Questions!

I didn't have time to try it but I will soon...
Regards,

Sylvain

Unfortunately the evaluations and conclutions in that thread were wrong. See post #15 here where I explain the reasons why it can't work.

Tom

 

[JB3DG]

And with 100+ switches....Thats why we need a alternative to using L vars for Right/Left clicks.

 

[JB3DG]

There is one other option....use unused FSX key events like the G1000 or the GPS key events to trigger custom events.

 

[sparouty]

And with 100+ switches....Thats why we need a alternative to using L vars for Right/Left clicks.

Hi,
I agree with you it's very frustrating to not being able to use (>K:xxxxx) call with custom event.
But I don't understand why you want left/right click for switch? Most of switch are 2 positions switch for which a single click is needed : a toggle behaviour...so custom event can be easily used.

Last I never noticed any issue with the use of Lvars in a vc whatever the mode used (single, mp, or sc): most of the Etendard vc animations are based on Lvars without any significant loss of fps... To my own point of view, Lvars are shared only in shared cockpit..
R.
Sylvain

 

[JB3DG]

We are talking about knobs and multi position switches here. Thats where the left/right click comes in. And having too many L vars will clog up a shared pit. Thats what we are attempting to prevent here....

Update:

I just thought of a another option. If you are using L vars for the animation of the knob/switch maybe one can send a value outside of the animation range and have it get reset by the key event in the gauge. Unless it makes the knob jump around that is....

 

[n4gix]

Ed,
10,100...1000...up to trigger_key_event(iEvent,iValue) is the same code, no extra lines needed. The only part that could become "heavy" is this one:

Neither event_handler or the L:vars need be monitored all the time. The only time they would need to be evaluated is when a mouse event of some kind was triggered.

IOW, every mouse action would set a triggered flag, the evaluation would run, custom key_event sent, L:var updated and finally the triggered flag reset.

-OR-

Alternatively, how about multiplexing a couple of unused SET type tokens and their associated variables?

 

[n4gix]

This is a very, very old thread, but somehow the method that actually works was never posted.

What Jon and I found is that by setting up one custom L:var we can easily use any form of mouse clicking and wheel rotations to send custom EventId hex numbers:

0x10001 (>L:Event,enum)

The event handler in the C gauge will monitor (L:Event,enum), then retrieve the value before resetting via 0 (>L:Event,enum).