Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

Comments in .lks file

How can I embed comments in the .lks file that will not be overwritten upon saving the file? Alternatively, how can I place my company information as part of the lookout application that cannot be modified by anyone else (i.e. the end user) modifying the application?
0 Kudos
Message 1 of 4
(3,535 Views)
Make the file read only, which also means that most changes will not be saved for re-compile.

THe best you can do really is with an Expression or a datafile that is read from. When we create systems we provide no method for the end user to modify the process (Admin is changed) unless specified.
Mike Crabtree - Lead Developer
Destek of Nevada, Inc. / Digital Telemetry Systems, Inc.
(866) 964-6948 / (760) 247-9512
0 Kudos
Message 2 of 4
(3,520 Views)
Hi fadihindi,

It sounds like you have two requirements: the first is to add comments to a .lks that will not be overwritten, and the second is to allow some sort of "restricted" development mode to ensure certain items are not removed.

1) In general, National Instruments does not recommend that you make changes to the .lks file directly unless it is absolutely necessary. When you edit and save a process in Lookout, the previous .lks file is overwritten by the editor, and therefore, any text comments that you have added manually using a text editor will be overwritten as well. There isn't a method to retain those comments from one version of the process to the next.

2) To allow for a restricted development mode in Lookout, you will need to set up different accounts for the different types of users you will have, assigning each user a level of accessibility. These user accounts can be set-up under Options>>User Manager. On your objects that are not to be modified (i.e. company information), set those objects to a higher level than certain users have access to. For example, Pot and Switch objects have a default security level of 0. But if you change those security levels to 10, and your end-user only has security privileges for 9, then the end-user won't be able to modify Pot and Switch objects. Note that Edit mode is only available to level 9 and 10 users.

For more information on setting up the security levels, refer to the Lookout Developer's Guide:
http://digital.ni.com/manuals.nsf/websearch/3D2A2AB4D33B681186256F0400607461

Since you are providing an application for an end user, you will have to be sure and set-up all the appropriate security levels on the end-users machine, to prevent certain items from being modified. You can't simply send the end-user the Lookout application without setting up the user accounts on the system.

Hope this helps.

Regards,

Jeff M.

Applications Engineering
National Instruments
0 Kudos
Message 3 of 4
(3,516 Views)
Thank you, I understand and use the policies that you mention. However, I am preparing a process for an end user that ultimately wants the capability of modifying the process, i.e., will be maintaining development and runtime licenses at the end location. Their intent is to be self-sufficient in making modifications to the process as their needs arise. All of this is fine except for that I need to be sure the process will not be used for other applications and would like to place some type of copyright stamp on it. Without delving into the legal issues, I want to somehow place a permanent "stamp" on the process that will identify it for its original application and purposes.

Unfortunately I already thought there would not be a solution for my issue, but I thought others might post their ideas on other ways to get this done. Thanks for any ideas.
0 Kudos
Message 4 of 4
(3,511 Views)