The code here is pretty convoluted and confusing. It looks like there’s an array of 4 PovAssgn objects which was (presumably) intended to represent the 2 devices x 2 shift-states… so far so good.
But then the triple-nested for loop attempts to writeout 2 shift states for each of those 4 PovAssgn elements?
The code is further complexified by what looks like a one-line hack to avoid writing SimDoNothing over a previously emitted callback… but that hack doesn’t seem to work.
The code is 90% duplicated then again below… for the case of pov hats on 2 separate devices. But I'm not sure I see why, the key file output should be the same. Only cfg entries would be different.
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/blob/master/Falcon%20BMS%20Alternative%20Launcher/Input/JoyAssgn.cs#L288
The code here is pretty convoluted and confusing. It looks like there’s an array of 4 PovAssgn objects which was (presumably) intended to represent the 2 devices x 2 shift-states… so far so good.
But then the triple-nested for loop attempts to writeout 2 shift states for each of those 4 PovAssgn elements?
The code is further complexified by what looks like a one-line hack to avoid writing SimDoNothing over a previously emitted callback… but that hack doesn’t seem to work.
The code is 90% duplicated then again below… for the case of pov hats on 2 separate devices. But I'm not sure I see why, the key file output should be the same. Only cfg entries would be different.