Follow-up Comment #4, patch #1640 (project wesnoth):
Some situations just require a straightforward volume change, and the "value"
attribute is for that.
For example, if we want to mute the music volume for a few events (i.e. set
the volume to 0), we can only do that with the "value" attribute.
Just pointing out that normal usage would be to only set "value" or
"relative", not both attributes at the same time. (although there is nothing
wrong with that either and the tutorial modification I uploaded has an
example of it happening)
About the "persist" attribute, sincerely I'm not sure if these changes would
have any use at all, or if they would just annoy the user. Nevertheless, I
decided to leave that option for scenario makers.
One advantage I was thinking of having changes persistent would be that the
music changes wouldn't be lost with load/save game. But I see your point, and
might remove the "persist" attribute if you find it more approppriate.
_______________________________________________________
Reply to this item at:
<http://gna.org/patch/?1640>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
