fly/fgdata
1
0
Fork 0
Code Activity

Make sure notifications don't stay in the outgoing MP emesary property, which could lead pilots just connecting to MP to get a past notification.

Browse source
This commit is contained in:
Nikolai V Chr 2020-10-19 00:40:05 +02:00
parent 407350229f
commit 7434c50ab9
1 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
Nasal/emesary_mp_bridge.nas
View file

@ -21,7 +21,7 @@
# Example of connecting an incoming and outgoing bridge (should reside inside an aircraft nasal file)
#
# var routedNotifications = [notifications.TacticalNotification.new(nil)];
# var routedNotifications = [notifications.TacticalNotification.new()];
# var incomingBridge = emesary_mp_bridge.IncomingMPBridge.startMPBridge(routedNotifications);
# var outgoingBridge = emesary_mp_bridge.OutgoingMPBridge.new("F-15mp",routedNotifications);
#------------------------------------------------------------------
@ -120,6 +120,8 @@
{
if (new_class.TransmitterActive)
new_class.Transmit();
else
new_class.TransmitEnd();
new_class.TransmitTimer.restart(new_class.TransmitFrequencySeconds);
});
@ -237,6 +239,12 @@
me.TransmitterActive = size(me.OutgoingList);
setprop(me.MpVariable,outgoing);
};
new_class.TransmitEnd = func
{
if (getprop(me.MpVariable) != "") {
setprop(me.MpVariable,"");
}
};
new_class.Transmitter.Register(new_class);
new_class.TransmitTimer.restart(new_class.TransmitFrequencySeconds);
return new_class;