Skip to content

add QtWidgets for forward compatibility with Qt5#31

Merged
dirk-thomas merged 2 commits intogroovy-develfrom
forward_compatibility_qt5
Mar 31, 2016
Merged

add QtWidgets for forward compatibility with Qt5#31
dirk-thomas merged 2 commits intogroovy-develfrom
forward_compatibility_qt5

Conversation

@dirk-thomas
Copy link
Copy Markdown
Contributor

This will enable most Python plugins to use the same code base to support Qt 4 as well as 5 with only minimal try / except for actual differences between the versions (see e.g. ros-visualization/rqt_common_plugins#359).

@wjwwood
Copy link
Copy Markdown
Member

wjwwood commented Mar 30, 2016

Seems reasonable to me.

So importing QtWidgets from the bindings is the same as QtWidgets and QtGui in Qt5, and is an alias for just QtGui in Qt4? Or is QtWidgets from the bindings just QtWidgets in Qt5?

@dirk-thomas
Copy link
Copy Markdown
Contributor Author

In Qt 5 the modules have the default meaning. For Qt 4 QtWidgets is an alias for QtGui - so both modules are "overpopulated" from the Qt 5 point of view.

@dirk-thomas dirk-thomas force-pushed the forward_compatibility_qt5 branch from 4d0ca72 to f71ce8e Compare March 30, 2016 23:59
@dirk-thomas dirk-thomas force-pushed the forward_compatibility_qt5 branch from f71ce8e to cfc0d24 Compare March 31, 2016 00:01
@wjwwood
Copy link
Copy Markdown
Member

wjwwood commented Mar 31, 2016

Sounds good.

@dirk-thomas dirk-thomas merged commit 5e6cbe9 into groovy-devel Mar 31, 2016
@dirk-thomas dirk-thomas deleted the forward_compatibility_qt5 branch March 31, 2016 22:00
dirk-thomas referenced this pull request in ros-visualization/rqt_common_plugins May 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants