--===============1808258082==
Content-Type: multipart/signed;
  boundary="nextPart1401670.Nk4JhUePEm";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1401670.Nk4JhUePEm
Content-Type: text/plain;
  charset="windows-1250"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 18 November 2005 01:32, David Powell wrote:
> Hi All,
>
> I've just upgraded to Mandriva 2006 (and along with that, Quanta
> 3.4.2). I'm getting a strange and annoying popup message whenever I
> edit a file I have recently saved.  So, for instance:
>
> 1. I open a file, make some changes, then save the file
>
> 2. I go back to the file, begin to make some changes and as soon as I
> start typing, a message pops up saying "The file was changed outside
> of the Quanta editor".

It doesnt happen here with Quana 3.4.2 from Suse or with 3.5 from=20
source.

> The strange thing is, I have not made any changes, outside of Quanta
> to the file.  Something else must be running in the background that
> is doing something to the file which causes a change, but I can
> assure you, I only have the file open in quanta.=20
It might be some deamon. Quanta gets the notice from KDE that the file=20
was touched. So something IS touching the file.

> "If you've got FAM running, disable it. ... I think turning of famd
> on my system helped a bit though."
>
> I don't have FAM running on either the Mandriva desktop (where quanta
> is running) or the Debian server (where the files are stored).

Do you have another file monitoring deamon instead of FAM (I don't know=20
the name, but there are some others as well)?=20

> However, on the debian 3.1 server on which the files are stored (I
> access them via samba)=20

I think samba is the problem. For some reason it might send a delayed=20
signal that the file was modified. I can imagine the following:
=2D you save the file
=2D you start to type
=2D only at this point samba notifies Quanta that the file was changed=20
(when you saved it).=20
=2D Quanta compares as a security meassure (exactly to avoid false alarms)=
=20
the file on the disk with the file in the buffer and it is different,=20
so it warns you

Try the following:
1) - save the file
    - wait a little and only type aftwewards
2) work on local files (not mounted shares) and  see if it happens or=20
not
3) try Quanta from 3.5RC1. It has a new method to detect if the file was=20
changed for real or not and this might be exactly what is needed.
4) try to find out if samba can be fine tuned to send notifications=20
immediately or to not send as all (as a workaround).

Andras
=2D-=20
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org

--nextPart1401670.Nk4JhUePEm
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBDfak4TQdfac6L/08RAhyvAKCnHnDmqsh3Npgx0bNjYHhryfdx9gCgnXh9
34PVCB6nuUr9ybDlgj4wWN4=
=uIxy
-----END PGP SIGNATURE-----

--nextPart1401670.Nk4JhUePEm--

--===============1808258082==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Quanta mailing list
Quanta@mail.kde.org
https://mail.kde.org/mailman/listinfo/quanta

--===============1808258082==--