It should be easy to read the notifications of sonar availability. Lead with the serial number.
Started listening...
ARIS 1549 + found at 192.168.10.180
ARIS 1004 + found at 192.168.10.168
ARIS 24 + found at 169.254.8.70
ARIS 24 - no longer heard
ARIS 24 + found at 192.168.10.144
ARIS 1549 - no longer heard
ARIS 1549 + found at 192.168.10.180
ARIS 1549 - no longer heard
ARIS 1549 + found at 192.168.10.180
ARIS 1549 - no longer heard
Current Behavior
As it stands, the messages are a bit jumbled and hard to read.
Started listening...
Found ARIS 1549 at 192.168.10.180
Found ARIS 1004 at 192.168.10.168
Found ARIS 24 at 169.254.8.70
No longer hearing from ARIS 24
Found ARIS 24 at 192.168.10.144
No longer hearing from ARIS 1549
Found ARIS 1549 at 192.168.10.180
No longer hearing from ARIS 1549
Found ARIS 1549 at 192.168.10.180
No longer hearing from ARIS 1549
Steps to Reproduce (for bugs)
n/a Examples provided above.
Your Environment
Versions used
ARIScope: n/a
Arisapp: n/a
ARISFish: n/a
ARIS Cmdr: n/a
Operating System and version on PC: Windows 10
Are logs available and would it be reasonable to attach them? n/a
Equipment used
AR2 or AR3? n/a
Joystick? n/a
ARIS: Explorer or Defender? n/a
If Defender, is it tethered? n/a
Context
The whole idea of arislog is to provide visibility into what's going on with sonar(s) on the network. Making availability messages easier to read helps rather than hinders.
Expected Behavior
It should be easy to read the notifications of sonar availability. Lead with the serial number.
Current Behavior
As it stands, the messages are a bit jumbled and hard to read.
Steps to Reproduce (for bugs)
n/a Examples provided above.
Your Environment
Context
The whole idea of arislog is to provide visibility into what's going on with sonar(s) on the network. Making availability messages easier to read helps rather than hinders.