JetBrains.Platform.UIInteractive.Shell.Common

GeneratedInternalTypeHelper

CreateInstance

GetPropertyValue

SetPropertyValue

CreateDelegate

AddEventHandler

NotificationPopup

Close Name Field

InitializeComponent

Wraps the Splash Screen HWND which was created by the bootstrapper for passing it into the application host so that the splash could be closed after the appication is ready to show the main window.

After the main window is ready, hides the splash screen.

In UI Interactive, actually processes menu items for mnemonics.

Line-breaking occurs if the line overflows beyond the available block width. However, a line may overflow beyond the block width if the line breaking algorithm cannot determine a line break opportunity, as in the case of a very long word constrained in a fixed-width container with no scrolling allowed.

No line wrapping is performed.

Line-breaking occurs if the line overflows beyond the available block width, even if the standard line breaking algorithm cannot determine any line break opportunity, as in the case of a very long word constrained in a fixed-width container with no scrolling allowed.

Display the element.

Do not display the element, but reserve space for the element in layout.

Do not display the element, and do not reserve space for it in layout.

Shares the way we get the dialog font (which is the default UI font in Windows, roughly - OK for use in fallback scenarios).

A string representing what should be displayed in Finder. A formatted string to show the specified item in Finder.

See . Also, if we're running in the mode that includes this assembly, winds up the automation providers automatically.

Call this method to enable all the automation peers.

Defines when IsTrimmed property is calculated

Default behavior

Immediate recalculation as anything changes

Emulates heavy freezes on the main thread, as if due to GC, swap, low machine specs, unfortunate init load, etc. to turn on.

Helpers for setting up exception reporting when the product shell is not running yet. User-interactive mode helpers.

An exception reporter which does not have the product context or any components yet. Shows a primitive message box without the submit-to-tracker capability. Reports failures in creation of the context for the full reporter. We MUST NOT obey flag here: after we have the context, we push another exception reporter that obeys the flag, but startup-related errors are most likely FATAL and MUST be shown to the user. — NOTE: not necessarily deemed true in wave01

Whether the model should be show to the user at all

Whether the user is logged in

Stores position (location + size) of owned dialogs relatively to the center of their owning window.

The distance of the child window center from the main/parent window center, in Avalon units.

The size of the child window, in Avalon units.

A screen point relative to the application main window. Wraps the type, but with some additional semantic.

The distance of the child window center from the main/parent window center, in Avalon units.

By default any UI application supports automatic updates, but does not show Updates option page.

The DPI Utility class which knows about the dynamic DPI. UI-interactive-aware, but not framework-specific.

The resolution in which the system has booted (or logged in the current session). On newer Windows, this might be fixed per application start time rather than logon time. If not , then all of the DPI values in the system will be equal to this. Since DPI is per-window, you should use DpiResolutions::From…() whenever possible. DPI can change in time, so use the live versions and apply changes. If you do not know the window/control you'd be used in, or you are currently not attached to any visual, use as the safest fallback.

Fires when any of the system DPI-related settings might have changed. For a window, this does not cover all cases because the window could have been moved to another display.

Gives _some_ DPI value which you should use when you cannot get the real DPI of the location. This might happen if your control has not been placed yet, or you are rendering without connection to the real UI, or if you are waiting to get the real DPI. The point is that you must use _some_ value anyway, and better it match the intended DPI otherwise there will be a mismatch or a resize animation. This should give the DPI of the application main window, if known, otherwise the primary display DPI.

Of all the current screen DPIs, the highest one. If you do not know the window/control you'd be used in, or you are currently not attached to any visual, use as the safest fallback. If not , then same as .

Gets whether the current environment supports dynamic DPI (as opposed to having it statically defined at boot / logon time).

Of all the current screen DPIs, the lowest one. If you do not know the window/control you'd be used in, or you are currently not attached to any visual, use as the safest fallback. If not , then same as .

Current DPI of the primary monitor. If not , then same as . Since DPI is per-window, you should use DpiResolutions::From…() whenever possible. DPI can change in time, so use the live versions and apply changes. If you do not know the window/control you'd be used in, or you are currently not attached to any visual, use as the safest fallback.

Should be called on OSes which support per-monitor DPI v1 not v2 (that's 8.1 and up to 10.0.14393).

Gets the current DPI resolution of the given monitor. Favors the per-monitor dynamic DPI, if applicable.

Gets the current DPI resolution of the primary monitor. Favors the per-monitor dynamic DPI, if applicable. This MUST NOT be used as the primary source for resolutions, but MIGHT be used as a sane fallback when the correct DPI retrieval has failed.

Originally, that were the boot time system DPI (hence ). Later on, Windows 10 April 2018 Update added a feature that it snapshots the primary display DPI at the moment a process is started as its per-process system DPI. And added the API. Theoretically, it's still static in the process lifetime, and should do. But hell knows their ideas. So let's call the function for sure (if OS is new enough).

Returns a system metric (which must be in pixels) in logical pixels (i.e. at 96 DPI).

Gets the screen DPI for a window at this moment, from the monitor on which it's currently shown.

Sets the current process as fully aware of per-monitor DPI.

Gets the min/max resolution of the displays currently available.

Gets the system-wide boot-time (or logon-time) screen DPI which does not reflect dynamic and per-monitor DPI changes.

When main window is known, submit its DPI provider here. The last item in the list wins over .

Creates hyperlinks from HTML-formatted links. Call for plain text pieces

Input text List of inline for

Creates bold inlines from text pieces in b tags. Calls for plain text pieces

Input text List of inline for

Creates hyperlinks from text pieces starting with http and inlines for plain text pieces

Input text List of inline for