-
Notifications
You must be signed in to change notification settings - Fork 1.8k
wxQt MDI fixes #25332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wxQt MDI fixes #25332
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the base class change of wxMDIChildFrameBase is unavoidable, could we use wxMDIChildFrame instead of wxFrameBase in the sample code? We try not to use wxFooBase in anything public, as they're supposed to be just an implementation detail.
Done (no idea what's going on today, but half of the CI builds fail with this error), but there seems to be a genuine build error in this job now. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
49b7cc0 to
bec80c1
Compare
This comment was marked as outdated.
This comment was marked as outdated.
|
Qt's main download site was down for almost a few days until early this morning. It seems to be working again, so the last commit isn't necessarily needed. That said, caching is currently broken in the official |
953767f to
956fde4
Compare
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates! This looks mostly good and could be merged as is, but I think it might still be improved a bit as indicated by the remarks below — but please let me know if you disagree.
649ee26 to
c9fda6e
Compare
|
Just in case you missed it, there is now a failure in |
5648148 to
bb469cf
Compare
If m_qtWindow is an instance of QAbstractScrollArea then the painter should paint on the viewport and not on the widget itself. Closes wxWidgets#25226
The QMainWindow widget will be created by wxFrame which wxMDIParentFrame derives from. This commit also contains some code formatting for consistency with wxWidgets style.
No real changes, this function will be used in the upcomming commits to avoid explicit static_cast<QMdiArea*> when working with m_clientWindow->GetHandle()
wxMDIClientWindow derives from wxFrame for its interface only for use in MDI and is not intended to be used as a real TLW.
Some of the code is taken from wxMSW port with minor changes.
This helps users to choose the preferred DI used by wxMDIParentFrame: - Layout::MDI (the default under Windows) - Layout::Tabbed (the default under non-Windows platforms) Currently the default is to use MDI on Windows and TDI elsewhere.
533cff8 to
6ebea3e
Compare
This comment was marked as outdated.
This comment was marked as outdated.
250c0d4 to
ec3e698
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Because using ASSERT_MENU_EVENT_RESULT, which uses wxMenuBase::SendEvent() under the hood, fails with wxQt on Linux. While the former seems to work on all platforms.
|
@AliKet , I just tried to test something else on my 3.2.7 code, but found something completely different. Start docview sample. You will get segmentation fault. Backtrace: I don't know if this is also addressed. Just wanted to mention it. If its not - its probably late anyway and most likely will need to be addressed in the new PR. |
That issue is addressed in this commit FYI, there are a lot of bugs/improvements in |
|
Just to be sure: this is ready to be merged, isn't it? Thanks! |
Yes, TIA. |
No description provided.