| Summary: | umbrello doesn't support interface class inheriting a class | ||
|---|---|---|---|
| Product: | [Applications] umbrello | Reporter: | greatbunzinni |
| Component: | general | Assignee: | Umbrello Development Group <umbrello-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/umbrello/3594c47da1e8f387f4985cdd272d762e9bc6248e | Version Fixed/Implemented In: | 2.20.1 (KDE Applications 16.08.1) |
| Sentry Crash Report: | |||
| Attachments: | interface class | ||
|
Description
greatbunzinni
2011-07-29 11:21:22 UTC
Created attachment 62340 [details]
interface class
Do you mean something like the attached class diagram?
Yes, if your IABC wasn't an abstract base class and instead a regular class. It appears that this problem affects more standard OO cases than this. For example, umbrello also refuses to acknowledge that an interface class may have a composition relationship with another interface class. This is absurd, as it means that it would be impossible to design an interface class which implements a State design pattern. Git commit b3b31402f662caafccd0133217f7af79154708de by Ralf Habacker. Committed on 01/09/2016 at 06:12. Pushed by habacker into branch 'Applications/16.08'. Allow compositions between interfaces. FIXED-IN:2.20.1 (KDE Applications 16.08.1) M +1 -0 umbrello/assocrules.cpp http://commits.kde.org/umbrello/b3b31402f662caafccd0133217f7af79154708de Git commit 3594c47da1e8f387f4985cdd272d762e9bc6248e by Ralf Habacker. Committed on 01/09/2016 at 06:12. Pushed by habacker into branch 'Applications/16.08'. Fix 'umbrello doesn't support interface class inheriting a class'. FIXED-IN:2.20.1 (KDE Applications 16.08.1) M +1 -0 umbrello/assocrules.cpp http://commits.kde.org/umbrello/3594c47da1e8f387f4985cdd272d762e9bc6248e |