?

Have you had any luck getting the weather to work on your TSW 105x's?

I have a client that really wants this to work on his panels. Weather seems to work fine when I connect remotely using the Crestron Go app bu he is stating the panels are an issue.

On Feb 27, 2021, at 11:58 PM, Troy Garner <troy_garner@...> wrote:

[Edited Message Follows]

Fair enough!

I think on the topic of CCD's, another thing I'd say is that their method is antiquated. They'd rather provide backwards compatibility instead of leveraging the real power that comes with 4-series and subsequently the full .NET framework without any sandbox. The concept is great, but now is in dire need of an upgrade! What I'm referring to is the use of separate AppDomains more specifically, and the ability to change the transport at runtime. (I know many people might not realize the benefit of having the transport switchable at runtime, but there's one massive benefit IMHO... The ability to switch the transport without a recompile! Imagine having gone through user acceptance training initially, then a couple months later they switch to a new model of a device that doesn't have IP communication and you have to switch over to serial. If you can isolate the change in code to a separate DLL, then you also mitigate the chance that a different compile of your program introduces bugs from a different version of the Crestron database. Who knows if different versions of SIMPL have bugs that would affect the recompile in an inadvertent way as well...)

I've had issues with CCD's and broken database versions in the past (affecting the wrapper symbols)... Other than that, the only other source of any bugs would be within the driver framework itself, or the driver itself.

--

?

Crestron Service Provider - TBD Enterprises Inc.

[Edited Message Follows]

1) If this is for a SIMPL# library used by SIMPL Windows, then you'll have to consider thread-safety here and race conditions. There's nothing wrong with the code from a single-threaded perspective, and for non-IDisposable objects you don't worry about it. Once there are no references to the object on the heap the GC will take care of it for you (unlike in a language like C or C++). Perhaps you want these two functions to be part of the same call chain? I don't see why they need to be different unless you're caching the data from the website for future callbacks within X amount of time since the last live poll...?

2) Realistically you could use LINQ here and the ToArray() method after a Where() clause to achieve this without creating a new List<T> from the FindAll() method. Same scenario as before, you don't worry about the memory allocation here for the most part. SIMPL+ will retain a reference to the array allocation for as long as it needs to use the data. (Also, if this is for search functionality, you can do the search in a case-insensitive manner using an overload of IndexOf().)

-- Off the top of my head, it would look something like this --

Ex: _allStations.Where(x => x.City.Name.IndexOf(CityName, StringComparison.OrdinalIgnoreCase) != -1).ToArray()

--

?

Crestron Service Provider - TBD Enterprises Inc.