Application.Run<T> isn't initializing properly by setting the `Application.ForceDriver` property

[BDisp]

As Run<T> is the only method used to start the application without needing to explicitly call Application.Init() it's imperative that the initialization should properly correctly if we want run an app with a certain driver than the default by setting the Application.ForceDriver property.

[tig]

I don't think so.

Instead of making the API more complex, I suggest you just use Application.ForceDriver instead.

It can be set in config.json as well.

[BDisp]

With the Application.ForceDriver using the v2win and v2net args I get the exception "System.ArgumentException: 'Invalid driver name: v2win. Valid names are CursesDriver, FakeDriver, NetDriver, ConsoleDriverFacade1, WindowsDriver'"`` by using the follow code. Can I change the title of this issue for at least fix this issue without adding driverName parameter?

Application.ForceDriver = args.Length > 0 ? args [0] : string.Empty;
Application.Run<ExampleWindow> ().Dispose ();

[tig]

Sure.

[BDisp]

I'll need to add the calledViaRunT parameter to the Init method. Will be a problem? Without this it will reset all the app variables, restricting the use of the Application.Iteration event, for e.g.