>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.
Have a look at the pyvcp button on either of the Tormach sample configs. >2. I still think this could be stored in a central data store rather >than integral to the HAL component itself. Agreed. I can imagine hard-to-find bugs arising from a hal pin saving off its last state. On the other hand, the persistent gladevcp issue becomes harder to solve. Where would that data be saved? Emc.var? Redis? Text file (like axis mdi history or touchy's preferences?). Redis seems like the winner to me, but I didn't perceive a groundswell of support for redis the last time it came up on the list. Rogge ------------------------------------------------------------------------------ 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
