 |
Marked as 'feature request' rather than 'minor bug'. Not sure how likely this is to get attention from devs, particularly as multiple workarounds exist using other software - including TARGET, but also with (many) other hardware interface programs. Still, it wouldnt be the first function added to BMS designed to work around limitations, if it did get added. |
 |
Thank you for your response. |
|
|
While I appreciate your report I honestly think this won't ever get any attention. Let me explain: The long vs. short press function are well described in the manuals. In addition there is an easy way to avoid any kind of trouble: DX. Yes, that might cause some work on your end but hey, we have a solution for you as well: Take a look at the Docs\01 Input Devices\03 HOTAS Setup folder and you might find what you need as a starting point. Editing is not very difficult. I even wonder why anyone would ever use Target instead of DX. But that's just my personal opinion. But even _if_ we would consider suggestions like that: Where to start, where to stop given the fact, that there are hundreds of possible input device combinations out there? In addition, we can't be held responsible for design flaws of third party programming software. :-) |
|
|
@Kolbe, do you work on the joystick input side of BMS? Im contemplating whether this would be better marked as "suspended" rather than "new", given that I agree with your assessment of how likely it is to get implemented. |
|
|
Good idea. Thanks for the heads up! |
- Anonymous
