Re: [Yade-users] [Question #691593]: avoid this message : "The constructor with a shareWidget is deprecated, use the regular contructor instead."

Question #691593 on Yade changed: https://answers.launchpad.net/yade/+question/691593 Jérôme Duriez posted a new comment: Thanks for sharing Luc, maybe it would help for possible future integration of this to (one choice to pick, increasing complexity) - send the output of a (git) diff to yade-..

Re: [Yade-users] [Question #691593]: avoid this message : "The constructor with a shareWidget is deprecated, use the regular contructor instead."

Question #691593 on Yade changed: https://answers.launchpad.net/yade/+question/691593 Luc OGER posted a new comment: here my modification which avoid the warning and still generates a graphical view : GLViewer.cpp line 64-65: GLViewer::GLViewer(int _viewId, const shared_ptr& _renderer, QOpenGL

Re: [Yade-users] [Question #691593]: avoid this message : "The constructor with a shareWidget is deprecated, use the regular contructor instead."

Question #691593 on Yade changed: https://answers.launchpad.net/yade/+question/691593 Luc OGER posted a new comment: just some complementary inormation: "After Qt 5.3's introduction of QQuickWidget, Qt 5.4 adds QOpenGLWidget, the long-awaited replacement for the legacy QGLWidget" from https://ww

Re: [Yade-users] [Question #691593]: avoid this message : "The constructor with a shareWidget is deprecated, use the regular contructor instead."

Question #691593 on Yade changed: https://answers.launchpad.net/yade/+question/691593 Status: Open => Solved Luc OGER confirmed that the question is solved: Dear Jérôme thanks for the hint where to find the 'solution': it is effectively inside the libQGLviewer 2.7.0 to 2.7.2 library, especia

Re: [Yade-users] [Question #691593]: avoid this message : "The constructor with a shareWidget is deprecated, use the regular contructor instead."

Question #691593 on Yade changed: https://answers.launchpad.net/yade/+question/691593 Jérôme Duriez posted a new comment: Hi, I guess it comes from graphical-display-related files like this one [*], which should be updated to account for a new behaviour of some third party library. At least, that