Hey @m.prestel, any documentation on those global variables like ptMouse?
No one know if this is possible?
Hey I want to access the Modbus slave diagnostic information, like in the ModbusTCPSlaveParameters dialog. Example of request counter and error counter.
Hey I want to access the Modbus slave diagnostic information, like in the ModbusTCPSlaveParameters dialog. Example of request counter and error counter.
Hey I want to access the Modbus slave diagnostic information, like in the ModbusTCPSlaveParameters dialog. Example of request counter and error counter.
Hey I want to access the Modbus slave diagnostic information, like in the ModbusTCPSlaveParameters dialog. Example of request counter and error counter.
But then for each visualization and instance/client, some objects and variables are available. There is no auto complete for those variables, how shall we know they exits? Before i was trying to access the mouse position via the interface for mouse event and then create a global variable array with a index for each client id. But if we have the ptMouse directly on the visu, then we dont event need that extra mouse event handling. Where is the documentation for those variables/pointers?
Hey Thanks Prestel. Knowing the mouse position relative to the screen already helps and allows me to program a function to be called before opening the dialog. So there is a reference pointer for the mouse position for each visualization, like there is the pClientData pointer. What other pointers exist? Where is this documentation?