ensightservice::SceneClientInit Struct Reference
Last update: 17.04.2023Request by the client for an EnSight scene update. More...
Public Attributes | |
| bool | allow_spontaneous = 1 |
| If true, EnSight is allowed to spontaneously start a scene update. If false, updates can only be initiated by the client via this message. | |
| bool | allow_incremental_updates = 2 |
| If true, EnSight is allowed/encouraged to send the minimal number of update packets. If false, the client must re-send the entire scene. | |
| int32 | maximum_chunk_size = 3 |
| Sets the maximum payload blocksize in bytes in a single UpdateGeom message (0=unrestricted payload size). | |
| bool | include_temporal_geometry = 4 |
| If true, request that the current temporal geometry be sent. If false, the current static view is sent. | |
Detailed Description
Request by the client for an EnSight scene update.
This SceneClientCommand sub message is sent by the client at startup or whenever the client would like a scene update. The server will respond by starting a scene update command sequence, beginning with a SceneUpdateCommand message, UpdateSceneBegin sub command. The update sequence will end with a SceneUpdateCommand message, UpdateSceneEnd sub command.
This message also informs the server what the maximum size of a block of data should be (in bytes). It also can be used to enable "spontaneous" scene updates that can be started by the EnSight server at any time. If the client would like the server to rebroadcast the entire scene, it should set the allow_incremental_updates flag to false, suppressing state cache tracking by the server.
Definition at line 183 of file dynamic_scene_graph.proto.
The documentation for this struct was generated from the following file:
- D:/ANSYSDev/NoBackup/branches/EnSight-Second-Coming/ensight/client/rpc_interface/dynamic_scene_graph.proto