minor issue: input format of Token

[lammel-hub]

Describe the bug Connecting by using a Token for a session instead of IP address and port is an elegant and simple approach. It seems the Token generated by Assistant always is 4 characters long and consists of numbers [0-9] and capitalized letters [A-Z]. However, when assisted enters a Token to initiate a session it allows for input of any characters, also outside valid ranges [0-9, A-Z] which generates an error message. This is a minor issue, but could be frustrating to an inexperienced or stressed assisted that may not immediately realize the difference or importance of typing the exact Token and could use the help.

To Reproduce Steps to reproduce the behavior:

1. Assistant: Go to Context: Connection. Function: Generate Token (illustrative example: "R8HE")
2. Assisted: Go to Context: Home. Function: Connect to Assistant
3. Assisted: enter the Token generated by Assisted, but do not use capitals (illustrative example: "r8he")
4. Response given by Assistant is "Invalid Token"

Expected behavior Context: Home

• Alternative 1: Function: Connect to Assistant accepts any Token input, but then automatically converts letters [a-z] to capital [A-Z] and removes any characters outside the valid ranges [0-9, A-Z] from the input string, before testing Token with server
• Alternative 2: Function: Connect to Assistant only accepts 4 characters length, automatically presents capital letters [A-Z] in the input box for Token (even if typed as [a-z]) and does not respond to pressed keys outside the valid ranges [0-9, A-Z]

Screenshots

• Alternative 1:
• Alternative 2:

Desktop (please complete the following information):

• OS: Win11
• Version 13 latest

Additional context The valid range of Tokens may be different.

[RetGal]

Good catch! As the tokens use an adaptive length, I'll simply convert the users input to UPPERCASE