Re: When to use a cross point
|
Even with someone else¡¯s program ROUTESYMSTAT makes tracing/debugging it much easier than many of the posts imply. ? If there¡¯s any level of complexity at all to the system I¡¯d rather deal with a somewhat sanely architected Crosspoint-based program than a somewhat-sanely architected layered buffer approach any day. ? -- Lincoln King-Cliby, CTS, DMC-E-4K/T/D Commercial Market Director Sr. Systems Architect | Crestron Certified Master Programmer (Gold) ControlWorks Consulting, LLC Crestron Services Provider | Biamp Audia Certified | Extron Control Professional ?
toggle quoted message
Show quoted text
From: Crestron@... [mailto:Crestron@...]
Sent: Wednesday, September 16, 2015 3:17 PM
To: Crestron@...
Subject: [Crestron] Re: When to use a cross point?
All who says it's "easy" to debug and trace through crosspoints, is neglecting one detail...
It may be "easy" to debug YOUR program, that YOU wrote, and YOU know the crosspoint scheme that YOU use on all YOUR systems, and have a reasonable logical system that YOU came up with and use.
It's is not so "easy" (and I say even more of a PITA), when you're trying to follow a program from another program.? When dealing with a program that THEY wrote, and THEY came up with the crosspoint scheme that THEY use on all THEY'RE system (and you don't), it doesn't matter if they there is a reasonable logical system that THEY came up with and use because it's different than yours and you have no idea what it is and have to figure it out (even assuming they didn't just use random crosspoint ID's that have no logical system to them).
In the first situation, if you like Crosspoints, you might think they are gold.? In the second situation, you WILL think they are not gold, but something of a more brown in color that has a unpleasant odor!
-jason
|
