Let's just be clear here you are disagreeing with Noel and how software works!
I wish I could show you my copy of Visual Studio and demonstrate it to you... anyways another day.
 

 
Cheers and peace to you :)

No, I am not disagreeing with Noel on what has happened and what has changed. Eventually, we got the complete story.  I am stating that X3D changed and caused a different behavior in mine and others work flow and thought I nailed the behavior change too btw.
 
I understand software development very well. I have been in mainframe programming, QA and Tech support for over 25 years. From a customer, end user POV, it does not matter if something is more correct. If it breaks something or changes the behavior in which something works without specific notice, customers are not real happy about it. I was indifferent, not happy or unhappy. I just wanted to know what the change was.
 
You being a developer does not change my opinion of what I and others think of this issue. Now if you said you were in Tech support and had great customer skills, I would have an issue with that. ;)
 
X3D changed, I asked what changed in reference to what I reported. Now I know.

Guitarmech111
Now if you said you were in Tech support and had great customer skills, I would have an issue with that. ;)

Touché!
 
Sorry, I'm outta here - but that was too good to not comment!

Conley you need to get into object orientated programming then and away from COBOL.
 
Quote Noel
 
What is broken here is that the plugin's are not sending the notification back to SONAR and this puts it out of sync. Now when you save the project we save the state that SONAR knows about which is incorrect and when you load it back you get the incorrect state that you are seeing.
 
However you are disagreeing with him! X3D changed but it DID NOT CAUSE anything!
 
I am stating that X3D changed and caused a different behavior in mine and others work flow.
 
So face it, you are totally disagreeing with Noel...
You have time and time again avoided what he has said in your response, and you never quote what he says, merely repeat what you think! :)
 
Your logic is flawed!!!
 
That logic is flawed. While it can be used as a thermometer for general troubleshooting, in the software world you cannot compare two different inter-operating components A and B and conclude that if a problem arises after a change in A it can be implied with certainty that the change in A is the root problem. In this case a change in A to add a new feature exposed a bug in B that causes the problem.
 
Are you going to acknowledge any of this or are you do you think if you say the same thing over and over again it will become true :)
 
What caused a change in your workflow was a bug in your plugin.
 
Anyway even I've run out of energy with this point... I keep editing it down, even resorted to capital letters, but I realise you don't actually want to read or understand what Noel actually said.
 

 
Cheers!
 
p.s. Thanks for the usual windup John and contributions... I state facts, you keep flinging the insults...

Anyway even I've run out of energy with this point.

 
 

CakeAlexS
Conley you need to get into object orientated programming then and away from COBOL.
 
Quote Noel
 
What is broken here is that the plugin's are not sending the notification back to SONAR and this puts it out of sync. Now when you save the project we save the state that SONAR knows about which is incorrect and when you load it back you get the incorrect state that you are seeing.
 
However you are disagreeing with him! X3D changed but it DID NOT CAUSE anything!
 
I am stating that X3D changed and caused a different behavior in mine and others work flow.
 
So face it, you are totally disagreeing with Noel...
You have time and time again avoided what he has said in your response, and you never quote what he says, merely repeat what you think! :)
 
Your logic is flawed!!!
 
That logic is flawed. While it can be used as a thermometer for general troubleshooting, in the software world you cannot compare two different inter-operating components A and B and conclude that if a problem arises after a change in A it can be implied with certainty that the change in A is the root problem. In this case a change in A to add a new feature exposed a bug in B that causes the problem.
 
Are you going to acknowledge any of this or are you do you think if you say the same thing over and over again it will become true :)
 
What caused a change in your workflow was a bug in your plugin.
 
Anyway even I've run out of energy with this point... I keep editing it down, even resorted to capital letters, but I realise you don't actually want to read or understand what Noel actually said.
 

 
Cheers!
 
p.s. Thanks for the usual windup John and contributions... I state facts, you keep flinging the insults...

X3D caused the change in the plugin behavior. If you had customer service experience, you would see my point. You are behaving like a developer though.  
 
I program in Assembler, REXX, XML, HTML, PL1, not much COBOL anymore.
Yes, lets let the thread breathe...

> X3D caused the change in the plugin behavior.
 
No the plugin caused the behaviour, X3D did absolutely nothing but expose an existing issue. If the plugin worked correctly there would have been no issue. That is exactly what the developer wrote, and you are attempting to say something else. There are other plugins that work fine aren't there? So this is a work of fiction. Nope, nope, nope. And "customer service" or even "customer" perception doesn't change what is a fact. Wrong perception is wrong perception.
 
I've had plenty of customer service experience, and the customer is always right until they are wrong! I never lie to my customers.
 
Looking at your development experience the gap in your knowledge is object orientated programming.
 
> Yes, lets let the thread breathe...

OK.

CakeAlexS
> X3D caused the change in the plugin behavior.
 
No the plugin caused the behaviour, X3D did absolutely nothing but expose an existing issue. If the plugin worked correctly there would have been no issue. There are other plugins work fine right aren't there? That is what exactly what the developer wrote, and you are attempting to say something else. This is a work of fiction. Nope, nope, nope.
 
I've had plenty of customer service experience, and the customer is always right until they are wrong!
 
Looking at your development experience the gap in your knowledge is object orientated programming.
 
> Yes, lets let the thread breathe...

OK.

The plugin changed nothing since it had not any code changes. I don't understand how you can't see that.
 
X3D changed the dynamics of SONAR and work flow with regards to preset processing. It will be an effort on CW and Waves for my issue. I am glad it has been figured out.

Do you agree or disagree with Noel's statement?
 
What is broken here is that the plugin's are not sending the notification back to SONAR and this puts it out of sync. Now when you save the project we save the state that SONAR knows about which is incorrect and when you load it back you get the incorrect state that you are seeing.
 
Now assuming you agree with this (do you agree with this?), ask yourself what would have happened if the plugin had actually sent the notification back to Sonar like other plugins do correctly with X3D, plugins that actually work correctly. Let me answer it for you, NO CHANGE IN YOUR WORKFLOW. X3D exposed a bug in your plugin.
 
End of.