Andrew Welker 19e799f11d fix: debounce device info events ... In some cases, multiple device info update events are triggering, causing the queue to be flooded with multiple unneccessary messages containing the same info. This clogs the queue and makes it harder for UIs to come online when Essentials restarts, especially in systems with a lot of NVX devices. The events are now debounced. If there are no new messages for 1 second, then the MC message is sent out.		2025-06-26 17:12:36 -04:00
..
PepperDash.Core	fix: return --- if the device was created without a name	2025-06-26 14:14:04 -04:00
PepperDash.Essentials	fix: add null check for room before adding to DevManager	2025-03-31 12:53:44 -05:00
PepperDash.Essentials.Core	fix: return --- if the device was created without a name	2025-06-26 14:14:04 -04:00
PepperDash.Essentials.Devices.Common	Update src/PepperDash.Essentials.Devices.Common/Codec/Cisco/IPresenterTrack.cs	2025-06-18 13:21:32 -06:00
PepperDash.Essentials.MobileControl	feat: return correct config for CS processors	2025-06-06 14:58:26 -05:00
PepperDash.Essentials.MobileControl.Messengers	fix: debounce device info events	2025-06-26 17:12:36 -04:00
Directory.Build.props	docs: first pass at using docfx	2025-04-25 21:39:45 -05:00
Directory.Build.targets	build: delete clz files on build	2025-04-04 08:09:42 -05:00