Daniel, Am 07.03.2013 um 17:32 schrieb Daniel Rogge:
> 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. great hardware example, I actually had that very issue (gearchange forgets gear setting) and that was one reason why I did gladevcp persistence -- the situation I was more thinking of when I wrote the question was: - HAL wires all sorts of things, most of which do not have state across sessions - some GUI components take part in the HAL game by being HAL comps proper with pins and all - there is no GUI application I could think of which does not have some 'Settings' or 'Preferences' tab - any 'Preferences' setting in a HAL GUI translates into 'HAL widget persistence required' to be usable - plus there may be other valid causes for state persistence, like the gearchange thing thats all that is to the justification for it - if the alternative is ticking checkboxes after each program start, that'd be a joke - and thats what we had - Michael ------------------------------------------------------------------------------ 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
