Plugins or not plugins

[MSpagni]

Trying to save a file that was processed by a plugin usually is not a good idea, so it's very good that EDP rises a warning.
I then click on the "use plug-ins" tool button, disabling the plugins and automatically recomparing the files (without plugins), then I edit the files and... "Warning, saving files processed by etc. etc."

The viceversa is true too. (And is also dangerous!)
If you enable the plugins after having already compared the files, then, even if the comparison was repeated with the plugins, you have no warning when saving.

[psguru]

I'm having troubles reproducing this (or perhaps I misunderstood your description). Could you provide exact steps please?

[MSpagni]

Indeed seems that the conditions to trigger the problem are no so trivial.
It's a bit late here, so please wait until I'll have a bit of time to experiment and my brain is more fresh. Now I need to sleep.
Sorry.
I'll keep you informed.

[MSpagni]

Here it comes.

Lets start by comparing a couple of ini files with plugins enabled.
Since they were processed by the plugins, click on the tool bar to disable the plugins.
The files are automatically recompared without plugins.
Now edit one (or both) of the files and try to save it/them.
The result is:

File ... was preprocessed by plug-in(s). What you are about to save is not based on the original file's content -- it's what you see on the screen, i.e. the result of running the plug-in(s) and your modifications. Do you want to proceed and overwrite the original file?

That's false, but at least you can tell EDP to proceed anyway.

I'm unable to reproduce the dangerous case, i.e. the opposite one.
When I try to edit I get (correctly):

The file you are about to change was preprocessed by plug-in(s). Any changes you make will be based on the output of the plug-in(s), not on the original file! Do you want to proceed?

Bottom line: there is only a minor annoyance in a non dangerous case.
What do I did saturday? I can't remember.
Should I encounter that problem again I'll try to write down immediately what I did.

Regards

[psguru]

Bottom line: there is only a minor annoyance in a non dangerous case.

Yes, I can confirm this as a bug. We'll try to get it fixed in the next build.

[psguru]

It's actually not so simple: making this change would potentially create dangerous scenarios in other use case. This means that we'll keep the current behavior in place, which is slightly annoying but at least not dangerous.

[MSpagni]

Ok, I can live with it.
What alarmed me was the opposit, but I can't replicate the problem.