11/14/2018 7:28 PM | |
Posts: 2826 Rating: (684) |
Starting with the documentation: The code you place into the library can be structured just the way you want - or almost. It can be loose standing code blocks but that would mean someone will have to integrate it into the master code. It is very flexible. Just keep in mind to make the integration more easy. Write a WORD document if that is what is needed instead of independent structure. Think about the dependencies. Global resources and UDT included. All those is best copied with the library, unless already available in the master. Be careful - the symbols used for code blocks should be unique. The block numbers is not always retained. That may need rework. Normally I have code blocks (read: standard functionalities used often) without DBs. Then these code blocks are copied into a master and integrated by hand. It can be new or sometimes it replaces an existing block. Have a look at a sample provided by Siemens: Seeing that it is software - - play with the library concept. Burning off some time for learning. Create the development project; it has to be done in any case. Structure it as you wish. Then start creating a library. Note a group of objects copied over together is grouped together in a single object. Use the library archive function. Then move over to a new project or a sample master project. Place the elements in the project and see what works easy and what is hard. Good luck. |
11/15/2018 7:54 AM | |
Posts: 32 Rating: (0) |
Good Morning! Thanks a lot for the help! Regards, |
This contribution was helpful to1 thankful Users |
Follow us on