There's an issue that needs group input. Currently there's a property value called y-offset (there's also an x-offset that isn't used much) and this parameter is used to initialize the panel position adjustment (shift F5 or shift F6). The default is 0.
Some of the panel xmls define initial values other than 0. This is done presumably to display panels that fall below the bottom of the window, even though none of them now actually have gauges or switches below the bottom edge of the window. What I'm getting to is this: The code in src/Cockpit/panel_io.cxx somewhere around line 705~708 doesn't allow subsequent panel loads (after the first one) to change the y-offset. This really makes panel coding a challenge, basically because the "offset" has been defined as non-zero in many cases, and this offset relates to the coordinates of all the objects on the panel. If we are using mini panel for example, it must have the same y-offset as the main panel or the gauges will be mispositioned because the coordinates relate to the other panel's y-offset. If the panel_io.cxx always (re)set the y-offset as defined by the panel being loaded then this issue would go away. IMHO all the code in a panel xml should work as designed when it is loaded, but changing this means that the y-offset will not be settable from the command line, which in very rare circumstances might be desireable. So I guess my question is this: can I change this to allow the panel xml to have final say on the y-offset even though there might be a user or two out there that sets y-offset elsewhere? Or am I underestimating the importance of this? Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
