Context Navigation

Changes between Initial Version and Version 1 of Ticket #2151

initial	v1
13	13	* You can't actually create multiple unique Local or LocalNative connections in the same application session. In the case of Maestro, after creating the first Local or LocalNative connection, you will actually have to restart Maestro in order to be able to create a connection with a different ini file.
14	14	* The MaestroAPI needs a way to programmatically check for this
15		* The Maestro Login dialog needs to guard against this. Basically once a Local/LocalNative connection has been created, do not show the connection UI. Instead the respective radio button should say "Connect to previous <Local\|TCP/IP> session" or something to that effect.
	15	* The Maestro Login dialog needs to guard against this. Basically once a Local/LocalNative connection has been created, do not show the connection UI again. Instead the respective radio button should say "Connect to previous <Local\|TCP/IP> session" or something to that effect.
16	16
17	17	For the general use-cases (a normal desktop/web application), this would rarely be a problem as the application is unlikely to be creating multiple connections to different providers. But Maestro (with its multi-connection support) exposes this problem wide open and needs to be gracefully handled.