Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic datalink configuration. #3181

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

DanAlbert
Copy link
Member

This is a stop-gap solution so we can get a release out that supports datalink as quickly as possible. It would be better to assign these early so the player can select which flights should be their team/donors, but for that we need to keep a registry in Game, plumb it through to each Flight creation (and there are many callsites for that), subscribe each flight to its datalink contacts (so disbanded flights do not remain part of a network), and of course the UI itself. That'll come later.

@codecov
Copy link

codecov bot commented Oct 3, 2023

Codecov Report

Merging #3181 (c73408d) into develop (32b3793) will increase coverage by 0.08%.
The diff coverage is 79.68%.

@@             Coverage Diff             @@
##           develop    #3181      +/-   ##
===========================================
+ Coverage    45.75%   45.84%   +0.08%     
===========================================
  Files          474      477       +3     
  Lines        25819    25880      +61     
  Branches      4521     4531      +10     
===========================================
+ Hits         11813    11864      +51     
- Misses       13985    13995      +10     
  Partials        21       21              
Files Coverage Δ
game/datalink/sourcetracknumber.py 100.00% <100.00%> (ø)
game/datalink/sourcetracknumberprefix.py 100.00% <100.00%> (ø)
game/dcs/datalinkconfig.py 100.00% <100.00%> (ø)
game/missiongenerator/aircraft/flightdata.py 82.60% <100.00%> (+0.79%) ⬆️
game/dcs/aircrafttype.py 45.93% <75.00%> (+0.48%) ⬆️
game/missiongenerator/missiongenerator.py 27.22% <0.00%> (-0.15%) ⬇️
game/missiongenerator/kneeboard.py 24.61% <0.00%> (ø)
...ame/missiongenerator/aircraft/aircraftgenerator.py 38.46% <33.33%> (-0.32%) ⬇️
...ssiongenerator/aircraft/flightgroupconfigurator.py 26.76% <28.57%> (+0.28%) ⬆️

@DanAlbert DanAlbert force-pushed the datalink branch 2 times, most recently from ae2707e to b1efa8e Compare October 4, 2023 04:52
This is a stop-gap solution so we can get a release out that supports
datalink as quickly as possible. It would be better to assign these
early so the player can select which flights should be their
team/donors, but for that we need to keep a registry in Game, plumb it
through to each Flight creation (and there are many callsites for that),
subscribe each flight to its datalink contacts (so disbanded flights do
not remain part of a network), and of course the UI itself. That'll come
later.

Follow up work:

* Filtering to only apply for the airframes that can use it
* Selection of team/donors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant