In the web configuration interface, you must enter the manager's call in upper case. When I mistakenly entered them in lower case, the queries controlling EM and TX didn't work. The queries themselves are converted to uppercase in the code, so ?em=? both ?EM=? works. Would it be possible to fix this in the next version, or in the web interface to point this out? Thanks!
In the web configuration interface, you must enter the manager's call in upper case. When I mistakenly entered them in lower case, the queries controlling EM and TX didn't work. The queries themselves are converted to uppercase in the code, so ?em=? both ?EM=? works. Would it be possible to fix this in the next version, or in the web interface to point this out? Thanks!
<!-- github-sync-id:2999669397 -->
Yes, like this. Or display the example (AB1CDE-1 AB1CDE*). That would just be a simple edit of .html text.
I guess it's just my stupidity. But it took me a long time to figure out why the other Queries work, but with EM/TX igate just sends ack and nothing happens. Many people in applications use their call in lowercase format (e.g. email, nick...).
Yes, like this. Or display the example (AB1CDE-1 AB1CDE*). That would just be a simple edit of .html text.
I guess it's just my stupidity. But it took me a long time to figure out why the other Queries work, but with EM/TX igate just sends ack and nothing happens. Many people in applications use their call in lowercase format (e.g. email, nick...).
<!-- github-comment-id:2810051665 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In the web configuration interface, you must enter the manager's call in upper case. When I mistakenly entered them in lower case, the queries controlling EM and TX didn't work. The queries themselves are converted to uppercase in the code, so ?em=? both ?EM=? works. Would it be possible to fix this in the next version, or in the web interface to point this out? Thanks!
do you mean to add a warning on the webUI or a way to save the stations only as uppercase String?
Yes, like this. Or display the example (AB1CDE-1 AB1CDE*). That would just be a simple edit of .html text.
I guess it's just my stupidity. But it took me a long time to figure out why the other Queries work, but with EM/TX igate just sends ack and nothing happens. Many people in applications use their call in lowercase format (e.g. email, nick...).
this warning will be added into soon to be released FW ;)