Nah, no custom tooltips anymore but allow styling. Have the standard ones translated and displayed with the associated shortcuts and thats it.
Tooltip attribute sounds good. Naming convention should be in line with <ConfigKey> http://mixxx.org/wiki/doku.php/midi_controller_mapping_file_format#ui_midi_controls_and_names This way we use these Key/Control names for Midi,Keyboard and Skins.
Some things to think on: * That <Visual> and <Text> are some kind of exceptions * That a button can have more than 1 <NumberStates> * To display tooltips for the <Property> field inside a <TrackProperty> node
If the tooltips get some polish, we should separate them from the library tooltips https://bugs.launchpad.net/mixxx/+bug/662540
It should be also possible to de/activate them from within the UI.
Nah, no custom tooltips anymore but allow styling.
Have the standard ones translated and displayed with the associated shortcuts and thats it.
Tooltip attribute sounds good. mixxx.org/ wiki/doku. php/midi_ controller_ mapping_ file_format# ui_midi_ controls_ and_names
Naming convention should be in line with <ConfigKey> http://
This way we use these Key/Control names for Midi,Keyboard and Skins.
Some things to think on:
* That <Visual> and <Text> are some kind of exceptions
* That a button can have more than 1 <NumberStates>
* To display tooltips for the <Property> field inside a <TrackProperty> node
If the tooltips get some polish, we should separate them from the library tooltips /bugs.launchpad .net/mixxx/ +bug/662540
https:/
It should be also possible to de/activate them from within the UI.