IO Tech #79
Merged
IO Tech #79
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tech progression API.
availability dates and ratings to correspond to the IO master tech advancement table.
Updating MML to stay working with MM
Updating MML to ensure works with latest MM jar
Conflicts: MegaMek.jar src/megameklab/com/MegaMekLab.java src/megameklab/com/util/UnitUtil.java
jar update
managing tech progression details.
setting minimum and maximum values.
stand/superheavy and ground/VTOL.
Finished conventional fighter as an option.
armor allocation view needs patchwork support.
Moved field guns into weapon panel and refactored infantry weapons into a separate class to simplify interaction with specialization secondary weapon restrictions.
primitive aero armor now comes at the end of the list.
movement, and and enhancements and added tech progression.
Show only the distinct manipulator name in the manipulators combo box.
longer part of the equipment name. And it's causing a StringIndexOutOfBoundsException.
mech mechanical jump jets as a JJ size because I failed to consider the fact that they require a size to be set and can't just be added as equipment.
trying to determine critical slots in summary view on structure tab.
unit. Increasing the number of troopers causes an IndexOutOfRangeException unless location arrays are resized.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removes almost all tech level and availability year data out of the ui and uses the tech progression data in MM instead, through the
ITechnologyandITechManagerinterfaces.Almost complete rewrite of the various structure tabs to consolidate redundant code and standardize. This is not strictly required by the transition to the new tech progression system, but the tech level and intro year data is so intertwined in the structure tabs that it was easier to do it all at once. With the exception of status and armor allocation views, which do not interact directly with tech data, each panel was refactored into a separate class which uses callbacks to send change information to the structure tab. In many cases multiple unit types can use the same panel -- the basic info panel is universal; the armor panel is the same for mechs, combat vehicles, and aerospace units, mechs and aerospace fighters use the same heat sink panel, and all units except conventional infantry use the same movement panel. Rather than convert back and forth between Strings and indices for the combo boxes, I've added some custom combo boxes that support parameters such as
EngineandEquipmentTypeand have support for prepending "IS" or "Clan" to entries as necessary when using a mixed tech base.