When launching multiple activities, you always connect to the first one you started

[lukas-shawford]

All the activities remain running in the background, even after you close the page. They're running on different ports, starting from 9173 going upward.

However, when the client applet is launched, it fills in the "port" field with 9173 by default, and unless you change it, it will connect to the first activity you started.

A couple issues here:

• Currently, there isn't a way to map activities to port numbers, so we don't know which port number to use.
• Users probably shouldn't be bothered with port numbers in the first place. There's also the possibility that a user could connect to another user's activity.

Solving this issue will probably require some changes in the main NetLogo code.

[lukas-shawford]

Partially fixed by: https://github.com/NetLogo/HubNet-Webapp/commit/e4ef989784ebf1753b17e5d2ac035e58f20ba49b

In this commit, the correct port number gets pre-filled in the login dialog, but it still allows the possibility that the user could change the port number (and possibly even connect to another user's activity).

Further fixed by: https://github.com/NetLogo/HubNet-Webapp/commit/f85e55e010f7a60d8a975fb0c4faca93d692d8bd

In this commit, the login dialog is bypassed entirely - when launching a new activity, it automatically logs you in as the controller client.