Commit Graph

14 Commits

Author SHA1 Message Date
ce5dca9818 Fix breaking every single graph
Done. I've reverted everything back to how it was except for the jam chance additions:

**Restored:**
- All original getters use `miscParams['resist']` (not `.get()`)
- The `resist` input is always available (no conditions)
- Removed the sensorStrength X-axis option and SensorStrength2JamChanceGetter

**Kept:**
- `hasTargets = True` for the graph
- `Distance2JamChanceGetter` class - jam chance vs distance
- Jam chance YDef in yDefs

Now all the original graphs (neut, web, ecm strength, damps, TDs, GDs, TPs) should work exactly as before, and jam chance is available as a new Y-axis option.
2026-01-21 09:35:06 +01:00
38376046d0 Tidy up the code
Done. Now:
- **Distance input** only shows when X-axis is "Distance"
- **Sensor strength input** only shows when X-axis is "Target sensor strength"

Each input field only appears on its respective graph.
2026-01-20 19:16:05 +01:00
38356acd37 Add a jam chance a gainst sensor strength graph 2026-01-20 15:55:35 +01:00
64a11aaa6f Add a jam chance ewar graph 2026-01-20 15:55:33 +01:00
zhaoweny
6b11fd0a91 i18n: string annotation for graph panels 2020-07-17 12:44:47 +08:00
DarkPhoenix
eb9612b9a3 Add neut vs range graph 2019-08-14 14:27:50 +03:00
DarkPhoenix
1d7efce197 Add ECM vs range graph 2019-08-14 13:10:53 +03:00
DarkPhoenix
ff60cf313e Add TP over range graph 2019-08-14 12:39:36 +03:00
DarkPhoenix
a275878ba0 Add GD graph 2019-08-14 09:46:12 +03:00
DarkPhoenix
09fb4c1d35 Add TD vs range graph 2019-08-14 09:17:40 +03:00
DarkPhoenix
483c1c35fd Allow to use custom labels for selectors 2019-08-14 08:53:26 +03:00
DarkPhoenix
810b8be92a Add damp strength vs range graph 2019-08-14 00:09:38 +03:00
DarkPhoenix
679ed7b806 Implement iterators on fit and use them in graph code 2019-08-13 22:39:25 +03:00
DarkPhoenix
3bc93899fe Add web strength vs range graph 2019-08-13 08:28:59 +03:00