Platform

Remarks: When false, prevents incorrect logic that may create multiple instances of Application or Platform in the same thread which can causes issues where handlers are no longer registered, etc. Multiple instances should still be able to be created in separate threads (for platforms that support it) when this is false.

Remarks: This sets this platform as current, and reverts back to the previous platform when disposed. This value may be null.

using (platform.Context)
{
	// do some stuff with the specified platform
}

Remarks: This detects the platform to use based on the generator assemblies available and the current OS. For windows, it will prefer WPF to Windows Forms. Mac OS X will prefer the Mac platform. Other unix-based platforms will prefer GTK.

Remarks: The platform ID can be used to determine which platform is currently in use. The platform does not necessarily correspond to the OS that it is running on, as for example the GTK platform can run on OS X and Windows.

Remarks: Typically you'd have only one platform active at a time, and this holds an instance to that value. The current platform is set automatically by the Application class when it is initially created. This will return a different value for each thread, so if you have multiple platforms running (e.g. GTK + Mac for OS X), then this will allow for that. This will be used when creating controls. To create controls on a different platform outside of its own thread, use the Context property.

Remarks: A desktop platform is usually used via mouse & keyboard, and can have complex user interface elements.

Remarks: A mobile platform is usually touch friendly, and have a simpler interface.

Remarks: This is used in platform detection to ensure that the correct platform is loaded. For example, the Mac platforms are only valid when run in an .app bundle.

Remarks: This is used to cache things like brushes and pens, but can also be used to cache other things for your application's use.

Remarks: This can be used to create a plaform instance for a secondary thread to show UI. It requires that the platform has a public constructor with no parameters. For example, you can initialize Eto for use in a separate thread (for platforms that support it) like so:

var app = new Application(Eto.Platform.Copy());
app.Attach();

var dialog = new Dialog();
dialog.ShowModal();

Note that Application.Instance will return the application instance for the current thread. If you want to invoke on the secondary thread when you already have a main thread, you will have to keep an instance of the new application instance manually and call Invoke/AsyncInvoke on that instance.

Remarks: This extension should be used when creating instances of a fixed type.

Remarks: This extension should be used when creating shared instances of a fixed type.

Remarks: This is called automatically by the Application when it is constructed

Remarks: This is useful when you are using multiple platforms at the same time, and gives you an easy way to execute code within the context of this platform, and return its value.

var mycontrol = MyPlatform.Invoke(() => new MyControl());

Remarks: This is useful when you are using multiple platforms at the same time, and gives you an easy way to execute code within the context of this platform.

Remarks: This is useful for 3rd party libraries and when defining your own custom controls. This method is called automatically on the same assembly of a custom control when its handler cannot be found. It will also be called for the same assembly with the prefix of the platform ID. For example, if MyControl was declared in MyControls.dll, then Eto will automatically also load MyControls.Wpf.dll for the Wpf platform, and MyControls.MacOS.dll for the MacOS platform, etc. Use ExportHandlerAttribute and ExportInitializerAttribute to register handlers with the platform when the assembly is loaded or perform other logic.