A quick note about the time field on the Route dialog. Interactive Maps uses the browser time field from HTML (type=“time”). This means that it is subject to the system Region and 24h clock settings of your system to get the 24H flight times properly. However the browsers and system don’t have their story straight and don’t all stick to the agreed standard and so you might see variations no how the time field is shown. I will try as much to normalize so all platforms are equal but this time field is a funky one. So be aware of the system settings to get it to show 24H time versus AM/PM and even that on some browsers/system will not properly work but the spec of time field says that should be the way it works.
@EuKeule would you be willing to put the source files on GitHub so others could expand on your work that was done already? As you already aware of how a community comes together to further code, projects, etc … when someone else doesn’t have the time people out there are just amazing and willing to help out.
For the apps that are listed in the bottom row of the launcher, once those apps are installed, are those icons supposted to act as program start buttons like the icons above (e.g. ICV host/Client and CFG (config).
I would like to learn how to implement the kneeboards per mission.
@airtex2019 Thank you very much! That certainly clarify things a lot more, I really appreciate it! I’ll do as you say, and keep experimenting with the key files (I made a back up of all the original ones in a different folder just in case anything goes wrong). Thank you very much for your time!
Thanks Tomcat! I’ve got MC and WDP working now, thanks to you. Weather Commander also appears to be working, but I get an “Unable to determine the version of your install” error when I start it up. I’ll keep at it.
And yes, I call them directories too, when the heck did that change, lol.
Thanks that you are checking out the documentation.
The docs follow the same purpose like BMS itself: come as close to real life as possible.
Our goal is to provide the most accurate documents in a quality which was never seen before. It is possible that espacially new documents (like the -1) may have some mistakes. Please post those issues here so we can improve: https://forum.falcon-bms.com/topic/23895/falcon-bms-4-37-0-documentation-bug-reports
The mentioned points are correct. If a system is not included in BMS (yet), we normally add a info about that. Take this as placeholders till the missing system(s) are implemented.
Toggle (for switches, knobs, buttons and functions):
Toggles through two (!) states of a switch, knob, button or function. Toggle >forward and toggle back (E.g. ON / OFF).
The buttons are behaving more like a Hold instead of Toggle:
Hold (for buttons and switches):
As long as you hold the button or switch, it is active. If you release the button or switch, it is inactive.
(e.g. EPU GEN Switch)
This one is also for functions which need a long input to become active. E.g. the EJECT Handle
Since this has been moved to the documentation forum, does that mean that it won’t be reassigned to be a toggle button, but the documentation will be changed to reflect its current state (a hold button)?