I think this plan is fine with the caveat that since this might significantly effect performance on low end machines, when you commit, make sure to email the dev-list. It does point to the question of do we have any dedicated low-end testers who can complain quickly if there is a performance hit? If so can we identify them?
On Tue, 13 Dec 2005 [EMAIL PROTECTED] wrote: > > Hmm, maybe it would be possible to implement this via an option in the > > graphics menu? This way we would have no problem if it really is a > > little slower. It is mainly need on big screens and most users that > > use big screens also do have rather fast machines. (>500MHz) > > When we make it an option the users are able to turn it off. Then > > there would be no problem even if we used trilinear interpolation. For > > users that think it is too slow it would be easy to deactivate it. > > Greets, > > Nils Kneuper aka Ivanovic > > > > > ok, this is what I plan to do (if it's ok with everybody) > > 1) test the patch at home, to check it works > 2) commit it and wait for complains (my machine is not a "slow" one) > 3) if there are no complains, fine > 4) else, revert it and add it back later as an option.. > > everybody is ok with this plan ? or would you rather have it as an option > anyway ? (no personal preference) > > > _______________________________________________ > > Wesnoth-dev mailing list > > Wesnoth-dev@gna.org > > https://mail.gna.org/listinfo/wesnoth-dev > > > > > > _______________________________________________ > Wesnoth-dev mailing list > Wesnoth-dev@gna.org > https://mail.gna.org/listinfo/wesnoth-dev > -- ------------------------------------------------------------------- "In theory, theory and practice are the same, but in practice they're different." ------------------------------------------------------------------- John W. C. McNabb -------------------------------------------------------------------
