Replies: 3 comments 4 replies
-
|
It's a sort of gateway to make sure things from the API are working. If we don't implement them because they don't work, that prevents folks from trying to use them and getting frustrated when things are broken or not working as expected 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Basically we don't want to limit users to a fixed list, but at the same time, we don't want to lose the benefits coming from a pre-defined list:
But as I said in the beginning, it's not really our aim to restrict our users but to try our best to provide as much stability and user friendliness as possible. We currently have a PR from RMROC for custom units, a branch from Pieter for variable dropdown, and I have some ideas in mind on opening up for any events/variables without scarifying our SimConnect optimization. However, I am taking a bit more time to think this through to make sure we can deliver the following features:
And I think I am almost there 😛. P/S: It took me too long to write this and RMROC beats me to it 😂. |
Beta Was this translation helpful? Give feedback.
-
|
Uuntil someone figures out a proper way to handle spamming any SimConnect requests as fast as you can push the StreamDeck buttons, the issues page would just be filled with more of these: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
When we want to add a new SimConnect variable, Structs.cs has to be modified. Can I ask why we just can't treat SimConnect variables as a string? That way, when a new variable comes along, the program won't have to be modified.
Beta Was this translation helpful? Give feedback.
All reactions