Skip to content

Conversation

@michaeldejournett
Copy link

We need to make sure that when the port unsuccessfully connects, that the error is still caught doesn't disrupt the user. I would intentionally disconnect the Gazepoint in the middle of a connection attempt and see if the program crashed.

@shbonita
Copy link
Contributor

@Joshua2000B would it be possible to test this on your end? Thanks. We want to make sure this work for both.

@Joshua2000B
Copy link
Member

I am currently unable to even get the GazePoint to connect now. The console is reporting the following error whenever I attempt to refresh the Eye Tracker list.

System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.77.161:4242
   at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
   at iTrace_Core.GazePointTracker..ctor() in C:\Users\jbehler1\Desktop\iTrace\iTrace-Core\itrace_core\GazePointTracker.cs:line 42
Gaze Point not connected!

@michaeldejournett
Copy link
Author

I am currently unable to even get the GazePoint to connect now. The console is reporting the following error whenever I attempt to refresh the Eye Tracker list.

System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.77.161:4242
   at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
   at iTrace_Core.GazePointTracker..ctor() in C:\Users\jbehler1\Desktop\iTrace\iTrace-Core\itrace_core\GazePointTracker.cs:line 42
Gaze Point not connected!

I think I know why you are having this issue, have you ensured that your gazepoint connection info matches what is in your gazepoint software.

@Joshua2000B
Copy link
Member

I changed the IP in GazePointTracker.cs, and I was able to connect. The issue is fixed, and the tracker worked great. However, we need to add the ability to change the GazePoint IP in the settings tab, as I was only able to get it to connect after manually changing the IP in Core's code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants