> Thanks, that gave me a baseline to work from.
>
> -1 to adding buttons for the mountain value. In another game, this kind of
> thing confused the hell out of me, because I never knew which other values
> would change when I pressed a button. This way, the user knows that the
> mountains are the first value that gets changed when you change one of the
> other values. Until you hit 0% / 100% anyway.
> --
>
> https://code.launchpad.net/~widelands-dev/widelands/bug-1378801/+merge/237599
> You are reviewing the proposed merge of
> lp:~widelands-dev/widelands/bug-1378801 into lp:widelands.
>
you are welcome!
But I still believe that a change in one parameter should invoke
adjustments in all other parameters. But I do not insist.
And I am really interesting in your solution. To me this is a programming challange. :)
mathematical/
2014-10-10 9:56 GMT+02:00 GunChleoc <email address hidden>:
> Thanks, that gave me a baseline to work from. /code.launchpad .net/~widelands -dev/widelands/ bug-1378801/ +merge/ 237599
>
> -1 to adding buttons for the mountain value. In another game, this kind of
> thing confused the hell out of me, because I never knew which other values
> would change when I pressed a button. This way, the user knows that the
> mountains are the first value that gets changed when you change one of the
> other values. Until you hit 0% / 100% anyway.
> --
>
> https:/
> You are reviewing the proposed merge of
> lp:~widelands-dev/widelands/bug-1378801 into lp:widelands.
>