Version: 1.1 OS: Linux I intended to draw a class diagram where an abstract base class (ABC) inherited from a class. This is the case where a user needs to implement a common base class based on a UI widget that must be used as an interface to other sub-classes. Yet, when I try to set an inheritance relationship that specifies an ABC inheriting from a base class, umbrello refuses that relationship to be set. Instead, it throws an error message warning that it is an "incorrect use of associations". It would be nice if umbrello didn't imposed any artificial constraints on a class diagram. Reproducible: Didn't try OS: Linux (x86_64) release 2.6.38-10-generic Compiler: cc
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