[Kde-games-devel] Cycling default (was: replacing classic tileset?)

Parker Coates parker.coates at gmail.com
Tue Mar 17 20:23:30 CET 2009


On Tue, Mar 17, 2009 at 15:07, Matthew Woehlke wrote:
> Parker Coates wrote:
>> On Tue, Mar 17, 2009 at 14:16, Matthew Woehlke wrote:
>>> Parker Coates wrote:
>>>> I had considered the KConfig approach as well, but the default.desktop
>>>> is used for more than just the case you describe. I also use it in the
>>>> case where the selected theme fails to load, or if the theme stored in
>>>> the config doesn't exist.
>>> Good point. Maybe you could change the fallback from "default", though?
>>
>> Yes, but ideally, I think we'd like a solution that let's us change
>> change the default without having to touch the compiled code.
>
> Yes, I considered that, but in that case I think you are right that we
> need everyone on-board and have to hide "default".
>
> (OTOH, from my perspective there isn't much difference changing a .cpp
> versus changing some other file :-).)

The difference is we don't let artists do the former, but we do let
them do the latter. :D

Parker


More information about the kde-games-devel mailing list