Removing unnessesarry checks causing port access conflicts.#196
Removing unnessesarry checks causing port access conflicts.#196michaeldejournett wants to merge 2 commits intodevelopmentfrom
Conversation
|
@Joshua2000B would it be possible to test this on your end? Thanks. We want to make sure this work for both. |
|
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. |
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. |
|
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. |
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.