Wt

Hello,

This is generally unwanted; the client can update the camera interactively several tens of times per second, which would cause undesired load if the server is not interested in this information.

Wt already supports synchronizing matrices client and server side, see JavaScriptMatrix4x4. When a server-side event handler is triggered from the client, the data of those matrices will be updated server-side to reflect their client-side state. So at the moment that the client decides that the server has to be informed of the contents of a matrix, you can simply trigger a JSlot, and the matrix data will be updated by the time your slot is invoked. You may want to implement your own camera handler if the server has to be updated of every client-side camera modification; at this time, the camera handlers don't fire events (or, at your option, only when the mouse button is released, maybe?).

We used this in projects to implement selection (intersection) tests on mouse clicks.

Wim.

You could use the mouseWentUp() or touchEnded() signals to see whether a drag ended. That way you know that the camera matrix may have changed.

Regards,

Roel