Dear Bogdan,
2013/3/7 Bogdan Marinov <[email protected]>
>
> This no longer will be a problem - I've bumped the version number of
> the defaultStarsConfig.json file:
> http://bazaar.launchpad.net/~stellarium/stellarium/trunk/revision/5875
Thanks to fix.
> This means that each version of Stellarium will try to read the file
> in the user data directory, find out that its version is off, and
> replace it with that version's own default copy.
>
> This is something that *should* have been noticed and done by Alex
> when he changed the file. It's a bug that would have affected a lot of
> people after the next official release, as the old
> defaultStarsConfig.json would have remained in their user data
> directory, pointing to the old file names - in other words, to files
> not in the installation. And, no, telling users to "reset their
> settings" when they show up to complain is not an acceptable solution.
>
*facepalm* I really don't seen version before because I was concentrated on
other possible troubles :'(
> What disturbs me is that this is another problem caused by
> Stellarium's lack of good developer culture - in this case, lack of
> attention and/or knowledge of the codebase and insufficient testing.
> At the moment, I can't offer a solution. The only thing that comes
> immediately to my mind is "shouting at people", but that won't be very
> productive. :(
>
Well, this is my big trouble :-/ Sorry.
--
With best regards, Alexander
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Stellarium-pubdevel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
