Daniel Horsey
2016-04-06 21:12:37 UTC
Hi Dan,
i don't think that there is any dependency between the hardware-mouse on the
server and the event handling at all.
--
Regards,
Marco
I've recently determined that the issue here is how the server is addressed:
I get this malfunction when I go to 'servername:portnum' (a resolved name).
If I call it as '###.###.###.###:portnum', the application works correctly,
and the mouse inputs are interpreted correctly. It's a workaround, but not
an answer as to why it happens. Any ideas?
-dan
I recently moved my machine running a witty application (the physical
location was changed). The mouse events have stopped functioning
correctly since the move. The only thing that changed was the mouse
attached to the server.
Did you also switch to a different Wt-Version?location was changed). The mouse events have stopped functioning
correctly since the move. The only thing that changed was the mouse
attached to the server.
i don't think that there is any dependency between the hardware-mouse on the
server and the event handling at all.
--
Regards,
Marco
I've recently determined that the issue here is how the server is addressed:
I get this malfunction when I go to 'servername:portnum' (a resolved name).
If I call it as '###.###.###.###:portnum', the application works correctly,
and the mouse inputs are interpreted correctly. It's a workaround, but not
an answer as to why it happens. Any ideas?
-dan