[Development] Using private API for qt-based library

[Fabrice Salvaire]

Le 25/09/2017 à 10:56, Viktor Engelmann a écrit :
>
> On 25.09.2017 10:29, iman ahmadvand wrote:
>> Hi every one.
>> I'm developing a set of specialized opensource widgets in c++ (called 
>> MaterialWidgets which is google material design implementation)
>> Now i want to use private API for this library to prevent re 
>> implementing a bunch of logics behind those widgets.
>>
>> What is your suggestion ?
> don't

Sure, but in some particular cases, we have no choice when Qt don't 
expose the API

>> As this lib depends on Qt, is it a bad idea to use private parts ?
>> Do you have other good design practice for me ?
>>
>> For a showcase 
>> <https://github.com/qt/qtbase/blob/dev/src/widgets/widgets/qabstractscrollarea_p.h#L76> i 
>> need to access 
>> QAbstractScrollAreaPrivate::scrollBarContainers->layout and remove 
>> scrollbars fromQAbstractScrollArea::viewport in my implementation.
>> Regards.
>>
>> _______________________________________________
>> Development mailing list
>> Development at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>
> -- 
>
> Viktor Engelmann
> Software Engineer
>
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> Viktor.Engelmann at qt.io
> +49 151 26784521
> http://qt.io
>
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin,
> Registergericht: Amtsgericht
> Charlottenburg, HRB 144331 B
>
> The Future is Written with Qt
> www.qtworldsummit.com
>
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20170926/99a651b1/attachment.html>