> 2) As it stands, it's very difficult for a new user to understand the > difference between Local Weather and Global Weather. let alone how > they inter-relate. Enabling the Local Weather package requires > setting "Enabled local weather module" from the Local Weather Settings > menu, yet the rest of the settings a user is likely to want are in the > Local Weather dialog. As a first step to sorting this out, I'd like > to do the following: > 2a) Move the "Enable local weather module" checkbox to the Local Weather > dialog.
In my opinion, a clean solution would be to introduce a new master weather dialog on which the user can specify * is live weather to be used or an offline solution * which weather system (local or global) is supposed to render the weather information (and supply the offline solution if applicable) Dependent on the setting in this dialog, the menu options for either Local or Global weather would then be available and the other greyed out. I think that would be the most intuitive structure. It would also prevent a user from discovering the hard way that he can enter whatever he likes for, say, visibility in the 'Global Weather' dialog, it won't ever show up whenever Local Weather is running. Such a solution would also allow for easy integration of a hypothetical third weather package > 2b) Move "Local Weather Settings" to the Debug menu, on the > assumption that more users will never need to modify the settings > there (Thorsten R. - is this true?) No - quite the contrary. The design philosophy is (not strictly true, but mostly): * Local Weather (i.e. what used to be Local Weather Tiles) is a launcher - everything you select here is parsed only at startup of the weather system, but cannot be modified runtime * Local Weather Settings contains all options which can be modified runtime. The main purpose is to get a handle on performance - for instance you might start out on relatively clear skies, so you can render clouds out to 55 km without large framerate impact - but then as you go on, you come into overcast skies, and the framerate drops like a rock - this menu allows you to choose runtime that you'd like to see clouds only to 20 km and get the framerate back So in my view, this should not appear in debug (for reference - I use the 'Settings' menu maybe 3-4 times per hour of flight or so). Cheers, * Thorsten ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
