You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Modal - The term used when describing a View that was created using the Application.Run(view) or Application.Run<T> APIs. When a View is running as a modal, user input is restricted to just that View until Application.Run exits. A Modal View has its own RunState.
In v1, classes derived from Dialog were originally thought to only work modally. However, Wizard proved that a Dialog-based class can also work non-modally.
In v2, we will simplify the Dialog class, and let any class be run via Applicaiton.Run. The Modal property will be set by Application.Run so the class can detect it is running modally if it needs to.
TopLevel - The v1 term used to describe a view that can have a MenuBarand/or StatusBar.
NOTE: There will still be an Application.Top which is the View that is the root of the Application's view hierarchy.
In v2, there is only one Application.Top. It is the View that is the first view in the application.
If a developer wants an "MDI" like interface, they can turn on the menubar/status bar in the Application.Top and add Window subviews to their hearts content. With the LayoutStyle.Overlapped each of those subviews overlap each other, support dragging/sizing, etc... They can add/remove subviews to the Application.Top, hide/show, etc... There is no need for a TopLevel class.
The text was updated successfully, but these errors were encountered:
tig
added
the
v2
For discussions, issues, etc... relavant for v2
label
Apr 4, 2023
Modal - The term used when describing a View that was created using the
Application.Run(view)
orApplication.Run<T>
APIs. When aView
is running as a modal, user input is restricted to just that View untilApplication.Run
exits. AModal
View has its ownRunState.
In v1, classes derived from
Dialog
were originally thought to only work modally. However,Wizard
proved that a Dialog-based class can also work non-modally.In v2, we will simplify the
Dialog
class, and let any class be run viaApplicaiton.Run
. TheModal
property will be set byApplication.Run
so the class can detect it is running modally if it needs to.TopLevel
- The v1 term used to describe a view that can have aMenuBar
and/orStatusBar
.In v2, we will delete the
TopLevel
class and ensure ANYView
can have a menu bar and/or status bar (via Adornments). See RefactorMenuBar
andStatusBar
to be adornments #2488NOTE: There will still be an
Application.Top
which is the View that is the root of the Application's view hierarchy.In v2, there is only one Application.Top. It is the View that is the first view in the application.
If a developer wants an "MDI" like interface, they can turn on the menubar/status bar in the Application.Top and add Window subviews to their hearts content. With the LayoutStyle.Overlapped each of those subviews overlap each other, support dragging/sizing, etc... They can add/remove subviews to the Application.Top, hide/show, etc... There is no need for a TopLevel class.
The text was updated successfully, but these errors were encountered: