They certainly don't *have* to be implemented separately. As you say, they
could be implemented by adding a NumberStates to each instance of a button
that is actually a switch within a skin.xml file (those without a value
could be assumed to be regular buttons)... But then you have to validate
when someone puts NumberStates to 1 or 3+... overall the effort would have
been more then the ~4 lines of code I implemented to add a switch, it
wouldn't be any easier to read the xml for humans either.
I also thought it made sense that something that looks/behaves like a light
switch ought not to be called a button.
On Jan 30, 2008 4:56 AM, Ben Wheeler <[EMAIL PROTECTED]> wrote:
> I still don't get why these have to be separate types. They seem
> basically the same to me, and whether a button acts as an impulse
> ("on" only) or a toggle ("on" and "off") seems like it should be
> a factor of its control's <NumberStates> in skin.xml, shouldn't it?
>
--
__
--- == __/ t.O ==--
http://stacktrace.org/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
