mirror of
https://github.com/dcs-liberation/dcs_liberation.git
synced 2025-11-10 14:22:26 +00:00
7648716199
The only parts of the old weapon data that worked well (didn't commonly result in empty pylons) did this implicitly, so make the grouping explicit. This also moves the data out of Python and into the resources, which both makes the data moddable and isolates us from a huge amount of effort and a save compat break whenever ED changes weapon names. I didn't auto migrate the old data since the old groups were not explict and there's no way to infer the grouping. Besides, since most of the weapons were *not* grouped, the old data did more harm than good in my experience. I've handled the AIM-120 and AIM-7 for now, but will get at least all the fox 3 missiles before we ship.
75 lines
2.9 KiB
Python
75 lines
2.9 KiB
Python
import logging
|
|
import operator
|
|
from typing import Optional
|
|
|
|
from PySide2.QtWidgets import QComboBox
|
|
|
|
from game import Game
|
|
from game.data.weapons import Pylon, Weapon
|
|
from gen.flights.flight import Flight
|
|
from gen.flights.loadouts import Loadout
|
|
|
|
|
|
class QPylonEditor(QComboBox):
|
|
def __init__(self, game: Game, flight: Flight, pylon: Pylon) -> None:
|
|
super().__init__()
|
|
self.flight = flight
|
|
self.pylon = pylon
|
|
self.game = game
|
|
self.has_added_clean_item = False
|
|
|
|
current = self.flight.loadout.pylons.get(self.pylon.number)
|
|
|
|
self.addItem("None", None)
|
|
if self.game.settings.restrict_weapons_by_date:
|
|
weapons = pylon.available_on(self.game.date)
|
|
else:
|
|
weapons = pylon.allowed
|
|
allowed = sorted(weapons, key=operator.attrgetter("name"))
|
|
for i, weapon in enumerate(allowed):
|
|
self.addItem(weapon.name, weapon)
|
|
if current == weapon:
|
|
self.setCurrentIndex(i + 1)
|
|
|
|
self.currentIndexChanged.connect(self.on_pylon_change)
|
|
|
|
def on_pylon_change(self):
|
|
selected: Optional[Weapon] = self.currentData()
|
|
self.flight.loadout.pylons[self.pylon.number] = selected
|
|
|
|
if selected is None:
|
|
logging.debug(f"Pylon {self.pylon.number} emptied")
|
|
else:
|
|
logging.debug(f"Pylon {self.pylon.number} changed to {selected.name}")
|
|
|
|
def weapon_from_loadout(self, loadout: Loadout) -> Optional[Weapon]:
|
|
weapon = loadout.pylons.get(self.pylon.number)
|
|
if weapon is None:
|
|
return None
|
|
# TODO: Fix pydcs to support the <CLEAN> "weapon".
|
|
# These are not exported in the pydcs weapon map, which causes the pydcs pylon
|
|
# exporter to fail to include them in the supported list. Since they aren't
|
|
# known to be compatible (and we can't show them as compatible for *every*
|
|
# pylon, because they aren't), we won't have populated a "Clean" weapon when
|
|
# creating the selection list, so it's not selectable. To work around this, add
|
|
# the item to the list the first time it's encountered for the pylon.
|
|
#
|
|
# A similar hack exists in Pylon to support forcibly equipping this even when
|
|
# it's not known to be compatible.
|
|
if weapon.clsid == "<CLEAN>":
|
|
if not self.has_added_clean_item:
|
|
self.addItem("Clean", weapon)
|
|
self.has_added_clean_item = True
|
|
return weapon
|
|
|
|
def matching_weapon_name(self, loadout: Loadout) -> str:
|
|
if self.game.settings.restrict_weapons_by_date:
|
|
loadout = loadout.degrade_for_date(self.flight.unit_type, self.game.date)
|
|
weapon = self.weapon_from_loadout(loadout)
|
|
if weapon is None:
|
|
return "None"
|
|
return weapon.name
|
|
|
|
def set_from(self, loadout: Loadout) -> None:
|
|
self.setCurrentText(self.matching_weapon_name(loadout))
|