mpower9;540734 Wrote: > I have had this happen to me as well. At the moment, I think the only > way to deal with the problem is to press the alarm button on the front > of the radio and deactivate the alarm before it goes off. > > Perhaps we should request this as an enhancement on the bug page.
I'd suggest you don't bother, honestly. The current alarm implementation is obviously quite buggy and I strongly speculate it will not get better. On the contrary, I proffer that it will only get worse as modifications like this one are added (if Logitech even chooses to attempt such modifications, which I think unlikely and/or unwise at this point). Every feature enhancement like this one (despite the request's very reasonable character) ends up being a band-aid modification to the existing alarm implementation. Because the architecture of the alarm system is wrong (yes, I say that definitively and with absolute conviction), every modification to the current implementation proportionally increases the chances that a regression in operation will be introduced. You can see how unstable alarms are at present... If this feedback causes any consternation then please go do a search for all the work I did previously in the context of fixing the broken Radio alarm system before bothering to chastise me. Every time Logitech touches the alarm functionality it is regressed (as you can see through objective evaluation of feedback on this forum in the context of new firmware releases). There are multiple reasons for this, but the primary overriding reason is as follows: - The alarm system architecture is plain wrong. No amount of fiddling with either the server (MySB.com or SBS) or the client (Radio) is likely to resolve this situation, as that same fiddling is clearly introducing more regression problems than resolutions. This is typically the case when a client/server application of any kind is inappropriately architected at the outset. Some may dispute the fact that I fixed the alarm system once (as best as was possible, considering the inappropriate architecture that was already in place). Yet, irrespective of their protests (and of Logitech's modifications to my implementation, which I warned against), I did indeed band-aid the alarm system to work properly at one time for the firmware 7.4.1 release. Much of my alarm system band-aid implementation code remains in the existing distributed alarm system today (that implementation has been changed by Logitech, however). The reality is that no band-aid on the Radio firmware side would have worked for long, however (even if my band-aid had been unmodified before public release), while changes continued to the server side of alarm operation. There are too many variables at play in the Radio alarm system operation, and like any client/server application that is initially architected incorrectly it will invariably suffer from instability and creeping regression as changes are incrementally introduced. Re-architecting it wouldn't be such a difficult thing to do, but apparently Logitech lacks the combination of time and/or incentive to do so. I would do it myself, but frankly have already fixed the Radio alarm system once and am weary of beating my head against the wall. I won't volunteer again to do it on my own time... Marc -- Marc ------------------------------------------------------------------------ Marc's Profile: http://forums.slimdevices.com/member.php?userid=34776 View this thread: http://forums.slimdevices.com/showthread.php?t=77945 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
