- Crestron simpl debugger update#
- Crestron simpl debugger pro#
- Crestron simpl debugger code#
- Crestron simpl debugger license#
Crestron simpl debugger code#
Add Extension Methods for IStreamDebugging to handle printing of tx/rx data based on conditionsĬurrent implementation requires a lot of code duplication in implementation of IStreamDebugging.Īdding interface extensions methods will make code more consistent and consolidated and clean things up. When utilizing a the GenericUdpServer, whenever shutting down the application, the error log shows "app shut down ungracefully", due to a blocking thread. The text should be printed to console instead of the bytes Startup debug message should not print unless DoNotLoadOnNextBoot is true -UdpServer causes app to shutdown ungracefully When stream debugging is enabled for the GenericTcpClient and the SendText method is used, the bytes for the text are printed to console instead of the string. Enabling Stream Debugging for GenericTcpClient should show text Wiki Documentation should be updated to describe this new explicit phase and best practices. Most existing devices in the Essentials Devices Common library and any plugin devices that communicate with 3rd party devices should eventually be updated to adhere to the new model. For devices where this process may be resource intensive, a user thread can be created to handle the initialization logic. The Initialize() method is where logic to start communicating with a 3rd party device, or to syncronize state with a device should take place. There already exists a DeviceManager.AllDevicesActivated event that EssentialsDevice should subscribe to and call the new Initialize() method. Add virtual Initialize() method to Device to handle starting device initialization / syncronization actionsĪt the moment, there isn't a clear best practice or delineation between the device activation phases, which should just be used to instantiate, register and associate device classes to get them ready to communicate, and a subsequent initialization phase, where devices should begin to communicate and synchronize state.
Crestron simpl debugger update#
Getting some null ref exceptions when adjusting stream please update with more detail (if you remember). Handling the comm method in the plugin factory for unsupported comm methods. There is a plugin that will require secure TcpIp communication implementing TLS1.2 and would like to have a comm method added to the enum to reference in the plugin factory without causing an exception for an unsupported comm method.Īdd a secure TcpIp reference to the eControlMethod enum. Is your feature request related to a problem? Please describe. XSigUtilityįorkers RBSystems bitm0de ngenovese11 savastiom Norgate-AV-Holdings-Ltd MersenneInteger wadepool leorassi mbarto33 xielong87 mvanmeurs ronpichardo Logic-Masters ChrisFarrantUK jchongslz Willis1776 tdwalden ricardo-leitao mikejobson os-rsingleton JaytheSpazz UMD-AV NUpchurchIMSTS PepperDashCore's Issues -Add Secure TcpIp method to eControlMethod enum As a library referenced by SIMPL+ wrapper modules in a SIMPL Windows applicationįor detailed documentation, follow this LINK to the Wiki.
Crestron simpl debugger pro#
Crestron simpl debugger license#
PepperDash Core (c) 2020 Latest Release License
0 kommentar(er)
