Hello,
I am trying to address a client request to "lock out" operators from making changes to a DeLogger project file.
The client wishes to restrict users to connecting to the host DT800 and viewing the mimic data.
Is there any feature within DeLogger 5 Pro which allows this?
Based on Google's cache of the previous forum (thank you, Google!) I have stumbled upon using Actions.
What I have so far is this:
PROJECT_LOAD("11600")
CLOSE_WINDOW("Text1.dlt")
CLOSE_WINDOW("Prog1.dl8")
CLOSE_WINDOW("Form1.dlf")
SHOW_WINDOW("Mimic1.dlm",0,2)
The above action run at startup in combination with turning off all status / tool bars gets me close.
Now I just need to get rid of the pesky Menu bar to prevent unauthorized opening/closing/saving/etc.
This can be accomplished by using the "Lock" command (CTRL+SHIFT+L) but I need to automate this using an action.
Is there an action macro command which "Locks" DeLogger? Is there a generic action macro to call keyboard shortcuts?
Is there anything else I am missing which can secure DeLogger from operator meddling?
Thank you for your help,
Matt
Caterpillar Tunneling Canada Corporation
Hello,
I am trying to address a client request to "lock out" operators from making changes to a DeLogger project file.
The client wishes to restrict users to connecting to the host DT800 and viewing the mimic data.
Is there any feature within DeLogger 5 Pro which allows this?
Based on Google's cache of the previous forum (thank you, Google!) I have stumbled upon using Actions.
What I have so far is this:
PROJECT_LOAD("11600")
CLOSE_WINDOW("Text1.dlt")
CLOSE_WINDOW("Prog1.dl8")
CLOSE_WINDOW("Form1.dlf")
SHOW_WINDOW("Mimic1.dlm",0,2)
The above action run at startup in combination with turning off all status / tool bars gets me close.
Now I just need to get rid of the pesky Menu bar to prevent unauthorized opening/closing/saving/etc.
This can be accomplished by using the "Lock" command (CTRL+SHIFT+L) but I need to automate this using an action.
Is there an action macro command which "Locks" DeLogger? Is there a generic action macro to call keyboard shortcuts?
Is there anything else I am missing which can secure DeLogger from operator meddling?
Thank you for your help,
Matt
Caterpillar Tunneling Canada Corporation