On 11/17/11 12:43 PM, Pierre Ossman wrote:
> Because it's a boolean. It has just the states true or false. There is
> no mechanism to see if the user didn't bother specifying anything (and
> I'm not sure that's desirable anyway). So we cannot map our three
> states to it ("always on", "always off", "auto").
>
> We could turn it into an int instead and have different values meaning
> different things. But I'm not sure it's worth it.
I think it would be worth it to have on, off, and auto. We always want
to offer the user the ability to override our decisions.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
