[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 143591] New: VCS action operates on wrong file when using split
From:       Paul Fee <pfee () talk21 ! com>
Date:       2007-03-29 14:58:17
Message-ID: 20070329165816.143591.pfee () talk21 ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=143591         
           Summary: VCS action operates on wrong file when using split
                    header / source view
           Product: kdevelop
           Version: 3.4.0
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: pfee talk21 com


Version:           3.4.0 (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
OS:                Linux

I've enabled split header/source view through:
Project/Project Options/C++ Support/Navigation/Enable split of Header Source files.

When I right click in the editor and select "Switch Header/Implementation" the edit \
window is split with two panes, one for the header and one for the source.

I have the project's version control set to "Perforce Integration".

Clicking in each of the edit panes will change the editor tab's label to reflect the \
filename (either header or source) of the file with focus.  The icon indicating \
whether or not the file is modified is also updated correctly.

However a right click on the tab and use of the Perforce menu will only perform \
operations of the original file, i.e. the file which the tab was associated with \
before the split view occurred.

The VCS actions e.g. edit/submit/diff need modified to take split view into account.

It's probable that this bug also affects other VCS options, i.e. CVS, Subversion and \
Clearcase, however I don't use these.

Thanks,
Paul


[prev in list] [next in list] [prev in thread] [next in thread]