[Qt-creator] perforce integration

[Matthias Ettrich]

That was a bug, it's fixed now. Of course creator should not lock files 
(unless there have been decoding errors). 

With the perforce integration, you can see that the file on disk is still read 
only, but you can start typing right away. When you save, you are given the 
choice to unlock the file in the scm (or simply to make it writable).

We think that's more convenient than loading the file read-only and forcing 
you to do a "p4 edit" when you start typing. 

Matthias



On Monday 24 November 2008 02:33:09 pm ext Joe Croft wrote:
> Hi Yall,
>
> Maybe Yall can define a set of fixed Source Control operations, Open,
> Revert, Check In etc then let the users define the command they want to
> use.
>
>  For me the auto checkout is not that big of deal, but the locked file
> would drive me crazy. Except for special cases, locked files are only
> really required for older systems such as VSS which can't do good merging.
>
> -joe
>
> On Monday 24 November 2008, Tom Deblauwe wrote:
> > Hello,
> >
> > The perforce integration works, however, there are some things that
> > could be better:
> >
> > - When I start editing a file, it isn't automatically checked out.
> > - When a file is not opened for edit, it is read-only. So when I open it
> > with CTRL+K, it is "locked". When I open it for edit, it stays locked. I
> > have to close and reopen it before I can type something in it.
> >
> > Thanks
> > Best regards,
> > Tom,
> >
> >
> >
> > _______________________________________________
> > Qt-creator mailing list
> > Qt-creator at trolltech.com
> > http://lists.trolltech.com/mailman/listinfo/qt-creator
>
> _______________________________________________
> Qt-creator mailing list
> Qt-creator at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator