Bug 159939

Summary: Files/Directories tree view in Kompare is not correct in some case when reading diff
Product: [Applications] kompare Reporter: Patrick ALLAERT <patrick.allaert>
Component: navigationpartAssignee: Kompare developers <kompare-devel>
Status: RESOLVED DUPLICATE    
Severity: normal CC: esigra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: diff file correctly rendered
diff file badly rendered
diff file badly rendered

Description Patrick ALLAERT 2008-03-27 09:06:23 UTC
Version:            (using KDE 4.0.2)
Installed from:    Gentoo Packages
OS:                Linux

The tree presenting the files and directories is most of the time wrongly created.

Lets have the following tree on the file system:

ROOT/
    A/
    B/

If you have no differences directly into ROOT (but in A/ and B/, cfr. buggy2.diff) you will see a tree like:

ROOT/A/
    ROOT/
        B/

This is also true if you have differences directly into ROOT but that comes after differences from A/ and B/ (cfr. buggy1.diff)

The tree is correctly rendered only if differences exist directly into ROOT and coming BEFORE differences from A/ and B/ (cfr. correct.diff)

To reproduce:

kompare correct.diff
kompare buggy1.diff
kompare buggy2.diff
Comment 1 Patrick ALLAERT 2008-03-27 09:07:34 UTC
Created attachment 24073 [details]
diff file correctly rendered
Comment 2 Patrick ALLAERT 2008-03-27 09:08:31 UTC
Created attachment 24074 [details]
diff file badly rendered
Comment 3 Patrick ALLAERT 2008-03-27 09:08:56 UTC
Created attachment 24075 [details]
diff file badly rendered
Comment 4 Patrick ALLAERT 2008-03-27 09:12:18 UTC
Oops, this one duplicates #139233

Note that this bug is present in both Kompare 3.x.y and 4.x.y
Comment 5 Kevin Kofler 2008-03-27 09:14:50 UTC
> Oops, this one duplicates #139233 

Right, I just came to that same conclusion.

> Note that this bug is present in both Kompare 3.x.y and 4.x.y

Indeed. :-(

*** This bug has been marked as a duplicate of 139233 ***