You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wesnoth-bugs opened this issue
May 8, 2017
· 2 comments
Labels
BugIssues involving unexpected behavior.ConfirmedIssues that have been successfully reproduced by at least one developer.WMLIssues involving the WML engine or WML APIs.
in 1.13-dev the bahviour of unit filter has changed to that [filter] id # "" [/filter] which previously didn't match any unit now matches all units. this makes a difference sometimes esp when you say [filter] id "$myunit.id" [/filter] it previously didnt match any unit if myunit didn't exist. Now it macthes any unit. Is the new behaviour intended ?
(Reproduced on windows)
Release: 1.13.0-dev
Priority: 3 - Low
Severity: 3 - Normal
The text was updated successfully, but these errors were encountered:
wesnoth-bugs
added
Bug
Issues involving unexpected behavior.
Confirmed
Issues that have been successfully reproduced by at least one developer.
Windows
OS-specific issues that apply to Microsoft Windows
labels
May 8, 2017
I looked into this -- the code which I most recently posted to master about unit filters treats id="" the same as if the id field were blank. I didn't realize that it was important not to do that. I think all the fields of unit filter that take comma separated lists are affected, so not just ids, but also types, variations, abilities...
Wedge009
added
WML
Issues involving the WML engine or WML APIs.
and removed
Windows
OS-specific issues that apply to Microsoft Windows
labels
May 9, 2017
BugIssues involving unexpected behavior.ConfirmedIssues that have been successfully reproduced by at least one developer.WMLIssues involving the WML engine or WML APIs.
Original submission by gfgtdf on 2014-08-24
in 1.13-dev the bahviour of unit filter has changed to that [filter] id # "" [/filter] which previously didn't match any unit now matches all units. this makes a difference sometimes esp when you say [filter] id "$myunit.id" [/filter] it previously didnt match any unit if myunit didn't exist. Now it macthes any unit. Is the new behaviour intended ?
(Reproduced on windows)
Release: 1.13.0-dev
Priority: 3 - Low
Severity: 3 - Normal
The text was updated successfully, but these errors were encountered: