This is a "comfort" feature request/wish.
Current Scenario:
When I clone my 737 MCP hardware instrument or add it to a panel, I have to set the hardware properties manually for each button, LED, encoder and displays. As it uses almost every pin of an Arduino MEGA, to enter all the settings it takes a few hundred mouse clicks and it is quite error prone selecting values from the drop down lists.
Future Scenario:
When I clone an instrument the hardware properties are copied / cloned together with the other instrument data/information. Either by default or by a general setting. Or as an alternative, copy it in a separate step.
Paul
Cloning Hardware Properties
- Keith Baxter
- Posts: 4685
- Joined: Wed Dec 20, 2017 11:00 am
- Location: Botswana
Re: Cloning Hardware Properties
Hi,
Best not to use “named” hardware.
Keith
Best not to use “named” hardware.
Keith
AMD RYZEN 9 5950X CPU, Corsair H80I cooler, ASUS TUF GAMING B550-PLUS AMD Ryzen Mother Board, 32Gb ram Corsair Vengeance 3000Mh, MSI GTX960 4G graphics card
-
- Posts: 236
- Joined: Sun Feb 14, 2021 6:55 pm
Re: Cloning Hardware Properties
I did follow the recommendations as stated in the WIKI: "Hardware Id's are not preferred, try to use named hardware instead."
Coming from a functional programming background, I also prefer doing things 'declarative' rather than 'imperative'. So it was natural for me to use 'named' hardware.
But given the current context for that proprietary hardware, your statement seems valid.
Coming from a functional programming background, I also prefer doing things 'declarative' rather than 'imperative'. So it was natural for me to use 'named' hardware.
But given the current context for that proprietary hardware, your statement seems valid.
Re: Cloning Hardware Properties
The statement on the wiki is a little mis-leading. I’ve advised a few people who are making hardware panels only for them to use the hardware id method as it obviously hard codes everything and can’t be lost or disrupted without a code change. Named hardware is absolutely recommended when sharing because it allows each user to configure their own hardware board and pin configuration.
It was a while back but I think I also suggested the wiki note be updated to reflect this thinking.
Tony
It was a while back but I think I also suggested the wiki note be updated to reflect this thinking.
Tony
Air Manager panels at https://www.experimentalsimavionics.com
Youtube Channel https://www.youtube.com/channel/UC8ZqXX ... kfZMq5BKig
Air Manager API Tutorial Video Series https://youtube.com/playlist?list=PLNr0 ... baT4gJKg5D
Youtube Channel https://www.youtube.com/channel/UC8ZqXX ... kfZMq5BKig
Air Manager API Tutorial Video Series https://youtube.com/playlist?list=PLNr0 ... baT4gJKg5D
Re: Cloning Hardware Properties
good point. and great explanation.Sling wrote: ↑Mon Jul 19, 2021 12:48 am The statement on the wiki is a little mis-leading. I’ve advised a few people who are making hardware panels only for them to use the hardware id method as it obviously hard codes everything and can’t be lost or disrupted without a code change. Named hardware is absolutely recommended when sharing because it allows each user to configure their own hardware board and pin configuration.
It was a while back but I think I also suggested the wiki note be updated to reflect this thinking.
Tony
Joe. CISSP, MSc.