Closed GoogleCodeExporter closed 9 years ago
Ubuntu 11.10
Original comment by vcos...@gmail.com
on 13 Dec 2011 at 10:15
Hi,
Does this happen every time you apply changes?
Do you only get the alert when applying changes from CSS-X-Fire, or do you see
it other times as well? I'm thinking of VCS operations such as update/revert,
external changes made from other programs, etcetera.
Are your project files stored locally or remote, or mounted on a network share?
If you click on "Show difference" in the dialog, do you see any differences?
Original comment by ronnie.k...@gmail.com
on 14 Dec 2011 at 7:55
"Does this happen every time you apply changes?"
Yes, every time. And the interesting thing is that first the changes are
applied, and after that the popup shows up.
"Do you only get the alert when applying changes from CSS-X-Fire, or do you see
it other times as well? I'm thinking of VCS operations such as update/revert,
external changes made from other programs, etcetera."
No, only when using CSS-X-Fire.
I use Git as VCS. But i'm not doing any external operations with it. Basically
all i do is make a few changes, then switch back so PhpStorm and apply changes.
"Are your project files stored locally or remote, or mounted on a network
share?"
Locally
"If you click on "Show difference" in the dialog, do you see any differences?"
No difference at all.
Original comment by vcos...@gmail.com
on 14 Dec 2011 at 8:06
I filed an issue at JetBrains a while ago since it could be an architectural
change in the IDE that is causing the error, and I have no possibility to test
it myself on Ubuntu: http://youtrack.jetbrains.net/issue/WI-8990
Original comment by ronnie.k...@gmail.com
on 15 Jan 2012 at 8:52
Do you have "Synchronize files on frame activation" enabled?
Original comment by ronnie.k...@gmail.com
on 31 Jan 2012 at 7:45
No.
Btw, in the 3.0.1 it works okay, so i don't know what it was, or some
degradation in the previous release or something else. So i think this ticket
ca be closed.
Original comment by vcos...@gmail.com
on 31 Jan 2012 at 8:36
Ok, thanks. Closing this since whatever the problem was, it was not caused by
this plugin.
Original comment by ronnie.k...@gmail.com
on 31 Jan 2012 at 8:53
Original issue reported on code.google.com by
vcos...@gmail.com
on 13 Dec 2011 at 10:15