Page 1 of 1

"replace" bug

Posted: 27.01.2005, 18:16
by Psykotik
I was pretty enthusiastic about the "replace" instruction, that my friend Jeamtag told me about. After trying on the earth, I was conviced that was the way I was looking for to get rid of my many textures added to "celestia\textures", and cleaning my HD.

BUT I just discovered managing this way textures will erase the moons... I cannot anymore to access the moon, phoebe, and so on.

Any clue ? I don't want to reverse back my changes made...

Posted: 27.01.2005, 19:56
by selden
I don't see how this would let you delete a lot of texture image files. If they're different, then I'd expect you'd want to keep them so you can see them all.

Anyhow, you might try using Modify, since that only replaces the individual declarations mentioned in the new object definition. Replace deletes the entire original object definition, which may be why the moons are being lost.

Posted: 27.01.2005, 21:36
by Psykotik
selden wrote:I don't see how this would let you delete a lot of texture image files. If they're different, then I'd expect you'd want to keep them so you can see them all.

By "cleaning", I meant keeping all my addons in "celestia\extras", not deleting them :) Upgrade would be a lot easier if I could keep "celestia\textures" untouched, without adding some files I would have check and copy when updating. Moreover, it would allow to keep the solarsys.ssc untouched too.

selden wrote:Anyhow, you might try using Modify, since that only replaces the individual declarations mentioned in the new object definition. Replace deletes the entire original object definition, which may be why the moons are being lost.


That's the point : I do not understand the way it works. If "replace" delete object depending on the "parent" object, I think the instruction is pretty useless...

Anyway, using "modify" instruction did the trick, thank you very much Selden. I can live now with that celestia behaviour :), but it would nice if the way of how "replace" works could be corrected.

EDIT : if I had better sought for, I'd had found Terrier's post pointing the genuinely same bug here :oops: [/url]