It combines the programming power of SIMPL (Symbol Intensive Master Programming Language), and the drag-and-drop functionality of Windows. A 0 keeps a signal permanently low and should only be used when you have a well-defined use case.Creston SIMPL Windows software offers every tool that is needed to test, program, configure, and debug an integrated control system application. Do NOT confuse this with putting a "0" on a signal. For things like "fb" signals and such, these still exist- you just aren't directly interacting with them. Remember that a comment "//" just means the signal isn't being told to do anything by your program. But it's good practice to keep your programs well-organized and efficient. Outside of a large program, are you likely to hit the handle limit? Maybe not. Your program has a limited number of handles available. This instructs the compiler to ignore the fact that the signal is not defined.Įvery time you add or define a signal, it uses up "handles" in your program. If you are not going to use a "required" signal, comment it out. If a symbol has optional signals, you do not have to fill those out. Symbols that MUST be completed (all signals filled) are marked with *!* in the name. It forces them to waste time looking for stuff that may or may not be implemented. When you hand off code to another programmer, tons of warnings/errors is very confusing. Some programmers may even use these as reminders of stuff remaining to do in the program.īUT any program you send into production should compile clean.
If you are testing out code or troubleshooting, warnings and errors are okay so long as the compiler can complete.
I tend to fill out most relevant signals on Crestron hardware so I can access it during debugging, but not literally everything, because there is actual program overhead involved if you have every signal on some big switcher hooked up, and most of those signals there's no chance you would ever need them during debugging. It doesn't actually comment out the signal or prevent it from doing things, it just hides the warnings. So if you have the output of one device going to //Signal_Name_1 and the input of another device as //Signal_Name_1 then that signal will actually work just as if it were called Signal_Name_1. So when you open up SIMPL debugger you'll be able to see those signals in debugger and interact with them, and they work just like normal signals.īe warned, they work just like normal signals. What it does is leave the signal in place, but doesn't give you the warnings. In crestron land, if you right click on the signal you'll see the description as "Disable 'No Driving Source'/'No Destination' Warnings" In normal programming that would comment those lines out, and they wouldn't exist. You can do that manually to each or by multiselecting and holding Alt+F2 Add // to the beginning of each of those signals.
0 kommentar(er)
