> > Hi BOb,
> >
> > Agreed - that solution would be rubbish.
> >
> > BUT, requesting the status of a file as soon as the modify event is
> > issued in a dev environment (i.e. developer starts changing file) &
> > warning the user that this is locked before they do too much work
> would
> > be a great compromise.
> >
>
> I still don't understand how this is useful. The *only* way locking
> works is if you lock the file before you start editing it. What if the
> file is not locked when you start editing it but *is* locked when you go
> to check it in?
>
> Further How is Tortoise to know that you have started to change a file.
> Unless the editor (or whatever you use to change the file) saves it on
> every single change there is no way for any other program to know that
> the file is changing. So for your scheme to work the editor would have
> to check the status of the lock and not Tortoise. And actually it would
> really want to check whether or not the file requires locking, not the
> lock status. Maybe our editor has some sort of macro facility that would
> allow this to be done?
>
This is the whole reason that locked files are read-only in the Working Copy. If it is read only your editor or IDE should tell you. This is a reminder for the user to get a lock. If they can't get a lock... well then... they are notificed.
BOb
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2599895
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-04-30 19:29:54 CEST