Bristol_Jonesey
This continual diatribe is doing nothing to solve his problems at all.
Ya got two users experiencing the same thing ... (See post 1 and 2) ... there is no solving it at this point. All they can do is send in a trouble report and hope enough people see it and complain about it and it gets resolved in the next patch. Although I have my doubts.
(*) I was just trying to bring some levity to the situation, and the OP did join in on it by the way, so I didn't think I was doing anything wrong.
If I would have chimed in and said, "Yeah, I've seen that kind of thing going on since X1 original release, it's not your system, it's just how the X series works.", then I would have got ridiculed for saying something bad about Sonar.
What the hell, here goes ... since you want to keep it a serious conversation ...
(
*) Yes, I have seen what Sharke described, starting with X1. It seems the longer you have a project open, the more times you open it, the longer you work with it, the more corruptible it becomes and you start to see annoying anomalies like he described until one day, the project just won't cooperate any more and you end up living with some old export you did 150 changes ago and call it a day.
But it's our system since Sonar works perfectly for the vast majority of users, right? Of course that's right.
Sorry for not agreeing. Sorry for agreeing.
Sorry.
@Sharke: I thought we were just blowing off steam and having some fun. Sorry if I derailed your thread. As a final word from me on the subject, yes, the entire X series does this from time to time in projects. It's best, in my experience, to scrap it and start over once this kind of weird thing starts because it only manifests in to something worse from there. Just my experience, as has been clearly stated, that's not the norm.
Have a good day.