On Nov 26, 2012, at 7:08 PM, Andre Somers <an...@familiesomers.nl> wrote:
> Op 24-11-2012 12:09, Nurmi J-P schreef: >> Hi all, >> >> Thanks to QStyleFactory and QProxyStyle, it is possible to instantiate and >> customize any available style. This is not limited to the built-in styles in >> QtWidgets, but also works fine for any style plugin since it nicely avoids >> the build time dependency to the corresponding style implementation. >> >> When it comes to the actual style implementations, we have quite a few >> refactoring ideas on the table. These ideas include class renames, possible >> merges and inheritance hierarchy changes. Not to mention the possibility of >> later on pluginizing certain styles to avoid loads of dynamic function >> resolving. These ideas are not feasible to implement in time for Qt 5.0, and >> for compatibility reasons cannot be done later if the style implementations >> remain in the public API. >> >> Hence we would like to take this opportunity to hide the following QStyle >> subclasses from the public API in Qt 5.0: >> - QFusionStyle >> - QGtkStyle >> - QMacStyle >> - QWindowsCEStyle >> - QWindowsMobileStyle >> - QWindowsStyle >> - QWindowsVistaStyle >> - QWindowsXPStyle >> > Does this also mean that you will remove void QApplication::setStyle(QStyle* > style)? This API seems useless if you can't create actual style instances any > more because they are public. On the other hand, I think that that may cause > issues for some applications... > > André One can still create style instances using QStyleFactory::create(), so I don't see any reason to remove this API. The -style <key> command line argument keeps working as well. -- J-P Nurmi _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
