There is one Overlay, but it has User Variables to Define if it is Pilot PFD or MFD. I will make basic Panel Art for single and dual (instruments) overlay panels. There is also the notion of CoPilot PFD in the Russ Barlows original work, but until I know what the differences are, I won’t implement it. The Autopilot button array on the left is also independently controlled (visible or not) meaning you can have AP off, on or on both, Not shown in the above I have a small Debugging flag in the top left of the display that says PFD or MFD so you know what mode your overlay is running in. It was useful for debugging when running a single overlay that both have all the same buttons. It has user-defined visibility so that purists can turn it off. I had hoped that I could do the two G1000 + Center COM Stack side by side but it makes the individual overlays too small / crowded.
I’m trying to decide if I do map panning now or later I have to see if Mobitflight even have events for this. The other big wish is to handle long button presses. I’ll ask about that later today.
I will say this significantly improves my Flight Tracker Button array layouts below on the Steamdeck, I need more encoders now (I have a plan for that)
The new code is better grouped/structured and more readable / commented especially in VS Code too BTW, that should make understanding it easier. If stuff does not make sense, feel free to ask questions.