2010/4/30 Vasco Névoa <[email protected]>: > Any setting that is changeable via GUI and doesn't get stored is VERY > annoying. > The reason I haven't spoken against this specific item (dim/sleep timings) > is because I think there is always bigger fish to fry, more critical bugs to > solve first, and I (wrongly) assumed the developers would think so too - but > I see too much innovation and not enough stabilization. Well... so be it, > you're not paid to do this, so I understand if you want to implement a lot > of shiny new gadgets in the framework instead of fixing nasty bugs. > Unfortunately, the SHR developers have been taking more and more usability > decisions without consulting the user community. I would like it very much > if they would poll the community before changing any usability aspect of > SHR. Not only the users may become dissatisfied/confused by changes, but we > also may have positive input to give. > If you choose to do this, do it in this mailing list, not on IRC. Most of us > do not have the time or opportunity to be in chat rooms. > Developers are not alone, and that does not have to be a bad thing. Leverage > your users. > Damn, this community needs a manager really bad... :/
Please try to avoid judging without knowing anything about what you're talking. With odeviced IT WORKED as you wanted - settings was stored and they were easly changable by SHR Settings UI. It changed when migrating from odeviced to fsodeviced, which is regression in FSO stack, not "usability decision"... BTW. Current dim values are OK for me, longer timeouts suck due to battery consumption :p -- Sebastian Krzyszkowiak dos _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
