30.10.2017, 17:18, "iman ahmadvand" <[email protected]>:
> Well.
> If it's OK to add new classes then we can create our classes And do the style 
> related things in private part until Qt6 release, on that time we can move 
> our changes to QStyle API.
> And also in this way the application setting will go away.
> in result:
> 1.We have our new widgets
> 2.We have overcame qstyle api changes
>
> On Mon, Oct 30, 2017 at 5:03 PM, Oswald Buddenhagen 
> <[email protected]> wrote:
>> On Mon, Oct 30, 2017 at 04:34:25PM +0330, iman ahmadvand wrote:
>>>    I was thinking of something like this to achieve:
>>>    QApplication::setStyle("material");
>>>
>>>    Which bring completely new styled and animated appearance.
>>>    That would be nice AND Qt way though.
>>>    But we've some new widgets beside the existing widgets, for
>>>    example: [...]
>>>
>>>    Which requires changes in QStyle enumerators.
>>>    The two build step was a good option but what about these new widgets ?
>>>    unfortunately it seems there is no way to porting this to Qt.
>>>
>> adding entirely new widgets (classes) can be done any time.
>
> But How? if it's not going to be a module ?

Just add new widgets to QtWidgets module.

>
>> the only challenge is that they may need new qstyle primitives, which
>> may then need custom implementations in the other styles as well. but i
>> guess "this widget doesn't look well unless you use the material style"
>> might be an acceptable policy.
>>
>> _______________________________________________
>> Development mailing list
>> [email protected]
>> http://lists.qt-project.org/mailman/listinfo/development
> ,
>
> _______________________________________________
> Development mailing list
> [email protected]
> http://lists.qt-project.org/mailman/listinfo/development


-- 
Regards,
Konstantin
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to