-
Notifications
You must be signed in to change notification settings - Fork 700
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
Overlapped broken on the v2_develop branch using the BackgroundWorkerCollection scenario. #3636
Comments
What I would prefer is for you to rewrite it. I will let you know when progress on #3634 is far enough long for you to do this. |
It it's to rewrite as a |
Do you agree we need a good multi-threading example for v2. |
|
The Threading scenario was created more for the threading examples. The BackgroundWorkerCollection was created to demonstrate more the MDI concept now called Overlapped. But I understand that the overlapped feature can work well with both concepts, although with different code:
|
Closing. I've added ensuring we have a good "Multiple overlapped, MDI-like views" example in #2491. |
Here is some of the issues after opening the scenario:
MenuBar
the keys navigations doesn't. Only work with mouse.MenuBar->View->WorkerApp
pressing F9 to opening theMenuBar
the menu isn't position correctly. See image:Work list:
is open. Press again F9 to open theMenuBar
and again the menu isn't position correctly. Seems that the application assumes that theMenuBar
is on the focused view (OverlappedChildren
) and not on theApplication.OverlappedTop
.Work list:
by clicking theClose
button and an exception is throwed. See image:MenuBar
and we click outside the menu on another toplevel, the menu stays opened and it must be closed to allows selecting the other toplevel.WindowsTerminal_TdVRQUqJwa.mp4
The text was updated successfully, but these errors were encountered: