Like I said, I'm sorry for bringing it up and I apologize for doing so. Qwt5 was great and I was enthusiastic about using it. Moving to Qwt6 would have required me to make big code changes as well as swallow coding conventions that disturbed me at the time, so I chose not to do it. I should have kept my opinions to myself and let others form their own.Try to step in my shoes for a moment
So I am sorry and will not mention it again. You have done a great service to the Qt community by adopting Qwt, continuing to improve upon it, and by participating actively in supporting those who want to use it on this forum and elsewhere. You've released it under license terms that allow its use anywhere, and haven't asked for fees for commercial use. It is admirable of you for doing it and your company for allowing you.
It goes beyond stable APIs. Somewhere between Qt 5.4 and later versions, disabled menu items stopped responding to hover events. I was relying on these events to enable / disable menu items based on my application state. When I switched to 5.5 or 5.6 (don't remember) users started to complain that they could no longer do things because the menus were always disabled. So I got stuck on 5.4.1 for a while until I decided to just enable everything and deal with it in other parts of the code.But this is a totally different story, one about stable APIs.
Probably the Qt organization has had just too many ownership and management changes over the past few years and they have lost some focus in the process. Software is coming out under the Qt banner that isn't well thought-out.
Yes, and it produces nice plots, but it is based on such an old version of OpenGL that it would require nearly a complete rewrite to bring it up to current standards. I don't know if I have tried building it with Qt5, so it might need more than just an OpenGL update.QwtPlot3D
Anyway, we've hijacked this thread, so maybe we can bury it and move on?
Bookmarks