mixxxdj/mixxx — pull request #179 by daschuer (2014-02-16 01:09:17+00:00)
Title: Wpushbutton default

In this PR, I have moved the connection setup in front of the widget setup. This way, the widget has all Information in its connection, to pick suitable defaults.
I have introduced a 0x4 *_DEFAULT flag, to indicate, that there are no user connection options set.
To reduce the complexity, I have removed the option to set a right button connection as display connection. The same function can achieved, by setting the "right button control" as no-button connection.

Now the no-button connection defaults to the left button connection, only if no button connection options are set. This way the skin designer has more control over what is emitted when. Here are the resulting Rules:

* A no-button connection defaults to the left-button AND display connection
* A left-button connection is also the display connection if not explicit disabled
* If there is a left button connection and a no-button connection, the no-button connection becomes the display connection
* A right-button connection defaults to a "from widget" connection only

Only the fist connected control is considered by the widget for e.g. toggle. So only this one receives the calculated defaults. Additional COs connected to the same widget function have to be set up manually.

I have removed the right/Left nature from the sliders and knops. Currently there are no alternative features implemented. This give us the freedom, to fix the touch issues an possible implement a well thought alternative function later.

It was also required to separate the property connection from the parameter connection.
The list of property connection is intended to connect COs to different widget properties, while the list parameter connections are allays connection to the same widget function. So it is better to have them separate anyway.