Alex Perry wrote:
> It would probably make things a lot simpler for the average user if
> FGFS included a wizard that automatically identified which
> combinations of features would be usable on a specific installation.
> Using that result as constraining logic in the menus would allow
> unusable features to be kept disabled and trivially cheap features
> (for the given hardware) to be kept enabled.
I think the biggest obstacle on this route is the fact that there's no
reliable switch for disabling certain features. Just think about
previous discussions on disabling shaders which: As far as I remember
the bottom line, disabling shaders relies on every shader honouring a
certain property. Some, maybe most shaders honour one property, others
honour a second property and even if you try to disable shaders by
toggling these properties, some are still getting activated because
they don't care about switches at all.
Selectively disabling features is probably not going to work reasonable
as long as the features in question are required to play nice in order
to get disabled, there's no such infrastructure as a "kill-switch" to
prevent the use/loading of *any* shaders (or whichever additional
feature).
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
