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

List:       kdevelop-bugs
Subject:    [Bug 120348] New: New class not assigned to correct subproject with the same name
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2006-01-17 21:20:29
Message-ID: 20060117222027.120348.sylvania () istop ! 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=120348         
           Summary: New class not assigned to correct subproject with the
                    same name
           Product: kdevelop
           Version: 3.2.2
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: sylvania istop com


Version:           3.2.2 (using KDE KDE 3.4.2)
Installed from:    SuSE RPMs
OS:                Linux

If you have 2 subprojects with the same name, there can be difficilties assigning a \
new class to one of them. For instance, I have a subproject tree that looks like \
this: +
> 
\foo
> \bar
\bar

If no target in \bar is the active target, then any class I try adding using the New \
Class wizard will be assigned to \foo\bar even if I select \bar. If I make a target \
in \bar active, then I will be able to add classes, however, in the Automake Manager \
- Choose Target dialog (which comes up when Ok is clicked in the New Class dialog) \
the Target: field indicates \foo\bar, which is not correct.


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