Just to be sure, you are not ruling out macro defined images such as
can be found in: data/units/Undead_Corpse_Walking.cfg ?
You just want to require the extension at the end, and it would still
be OK if the base_name is a WML macro variable? That would be fine
with me. Not allowing the base_name to be a macro variable has
certain problems that I would object to.
Overall, at first glance this seems like a reasonable request. I
don't know if there are any active C++ coders who are familiar with
the file path code, however, so it will likely require finding someone
willing to code-dive and figure out how it works, which will likely be
a bit of work.
Darth Fool
> The thing I most want abolished is the option to have the WML
> autocomplete the file extension. Or, to put it another way,
> macroscope needs all image file references to be detectable in a
> context-independent way with a regular-expression match, rather than
> by requiring a WML-aware parse of the file. The easiest way to do
> this is to require that all references have one of a small set
> of recognizable suffixes like ".png", ".wav", ".ogg", and ".jpg".
> Adding to that set of extensions is not a big deal, but the set
> has to exist for any tool like macroscope to have a prayer of working.
--
-------------------------------------------------------------------
"In theory, theory and practice are the same,
but in practice they're different."
-------------------------------------------------------------------
John W. C. McNabb
-------------------------------------------------------------------
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev
