On Thu, 7 Mar 2013 17:06:32 +0000 andy pugh <bodge...@gmail.com> wrote:
> On 7 March 2013 16:32, Daniel Rogge <dro...@tormach.com> wrote: > > A simple example: > > > > The hal gearchange component allows people to select different > > scales for speed commands. Without persistence the gearchange.sel > > pin comes up in the same state every time, even though the user > > likely wants it to come up in the last used state. > > But surely it gets set to the correct value by the gearlever > microswitch approximately 1mS later? Assuming there is a micro-switch. If not, it would be nice if the last known position was remembered. 1. Even if it's remembered, there's a chance that the transmission could be shifted while the control is off, thereby getting things out of sync, so some way to correct this must be provided. 2. I still think this could be stored in a central data store rather than integral to the HAL component itself. Thanks, Matt ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
