URL:
http://gna.org/patch/?3483
Summary: The way default tileset is selected
Project: Freeciv
Submitted by: cazfi
Submitted on: Mon 06 Aug 2012 12:35:16 AM EEST
Category: client
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Planned Release:
___
Details:
Now that default tileset selection by priority is fixed (it was selecting
first in alphabetical order) it became even more apparent that this needs to
be rethought.
The selection does not discriminate between sources where tileset is from -
it's not necessarily one of the tilesets we ship with. I just got ancients
tileset when launching new installation (freeciv-modpack used first to grab
custom modpacks), which even isn't compatible with default rulesets.
The problem is not caused by the priority fix - but when selecting by
alphabetical order, there wasn't any (widely used) tilesets before Amplio.
So, I think we should get rid of the priority concept, and provide name of the
default tileset in code. To make future migrations to new default tilesets to
work better, special value default similar to metaserver setting should be
used.
Anyway, while we wait for freeciv fix for general case, quickfix to reduce
ancients tileset priority should prevent it from claiming default tileset
status in more installations. I'll update versions available via
freeciv-modpack asap.
___
Reply to this item at:
http://gna.org/patch/?3483
___
Message sent via/by Gna!
http://gna.org/
___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev
