This is the mail archive of the xconq7@sources.redhat.com mailing list for the Xconq project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I'll try building a best_image_in_range function in the kernel - that
should be easy - but I'm not sure about the interface side of the
equation.
I think that there's a TCL command implemented for the purpose
of requesting unit images (possibly even the same one you were looking at
with those crashing bugs I filed recently)
and that command will need its
syntax changed or something to deal with the additional arguments, and
then the TCL code that actually uses that command will need to be updated
too.
Now, if there isn't an image in the range and it has to scale, to what size should it scale? I'm thinking maybe it should go to the largest end of the range - it's going to look blocky for being scaled anyway, so it might as well at least be big - but would it be better to have a third width/height pair as well, to be the size to scale to if scaling is necessary?
Low-res pixel color problem = the issue of some terrain types disappearing at the lowest magnification, right?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |