mitch91175
2500 Club Member
- Joined
- Mar 23, 2014
- Messages
- 2,831
- Reaction score
- 2,194
- Location
- Rowlett, TX
- What state or country do you live in
- Texas
I posted this same message in the Neptune Systems forum, but wanted to get you guys opinion and let me know if I am missing something:
I have made some changes to my programming and it is a pain having to go through each outlet to determine if something is being used. I know that I could use "Profiles" instead, but at the same time just programming something directly to the outlet work best (even knowing what is dependent on the profiles helps).
Wouldn't it be awesome if there could be a "Dependencies" list when you are viewing an outlet/profile, etc.?
That way when you are programming, you do not forget something. Similar to how SQL Server and other programming languages show you what items are dependent on the table/view/stored procedure.
I would imaging that it could be something that wouldn't be too difficult to accomplish and would DEFINITELY make programming much easier from a standpoint of knowing what is dependent on what and assist with preventing some potentially major programming mistakes.
Thoughts?
For instance: I removed one of my leak detection probes and replaced it with an optical sensor. The 2 have totally different purposes and if I hadn't gone through all of my outlets, bad things could have happened. Pumps could have shutoff, ATO wouldn't have worked, skimmer would have shutdown, the list goes on.
I have made some changes to my programming and it is a pain having to go through each outlet to determine if something is being used. I know that I could use "Profiles" instead, but at the same time just programming something directly to the outlet work best (even knowing what is dependent on the profiles helps).
Wouldn't it be awesome if there could be a "Dependencies" list when you are viewing an outlet/profile, etc.?
That way when you are programming, you do not forget something. Similar to how SQL Server and other programming languages show you what items are dependent on the table/view/stored procedure.
I would imaging that it could be something that wouldn't be too difficult to accomplish and would DEFINITELY make programming much easier from a standpoint of knowing what is dependent on what and assist with preventing some potentially major programming mistakes.
Thoughts?
For instance: I removed one of my leak detection probes and replaced it with an optical sensor. The 2 have totally different purposes and if I hadn't gone through all of my outlets, bad things could have happened. Pumps could have shutoff, ATO wouldn't have worked, skimmer would have shutdown, the list goes on.
Last edited:
