Hi,
On 06.07.19 19:59, Adrien Ollier wrote:
....
Well IMHO the problem that you even have to think about this is that
OutputDevice is a enormous class, and then you have to deal with another
even more enormous subclass vcl::Window, which should never be a subclass
of OutputDevice in the first place. However the work to change that is
quite big and non-trivial. Once that is done I'm sure the need that a user
needs to know with what subclass of OutputDevice it deals with will be
mostly gone. Until then I'm also comfortable with the status quo and still
have the enum and work with conditions for the outside use. From inside the
hierarchy of course it is better to use polymorphism.
Regards, Tomaž
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.