Re: [Mixxx-devel] Latenight widgetgroup borders

2015-06-26 Thread Ferran Pujol Camins
Excuse my stubbornness but: I've already managed to correct the border issue, thank you. I'm now trying to implement Mel's idea. My first naive solution is a new button at the left side that toggles the visibility of the others. This has the problem that the number and size of buttons is still limi

Re: [Mixxx-devel] Latenight widgetgroup borders

2015-06-26 Thread Thorsten Munsch
In this case you could use the space of the crossfader and the mixxx logo for three, nearly four, rows of the library.. Btw. I'll submit my changes again this evening or tomorrow. :) Am 25.06.2015 um 17:12 schrieb Owen Williams: Removing the crossfader is irrelevant for helping screen heigh

Re: [Mixxx-devel] Latenight widgetgroup borders

2015-06-26 Thread Be
There already is the View menu. I am in favor of getting rid of all the on-skin buttons and keeping all those options in the View menu. On 06/26/2015 10:52 AM, Ferran Pujol Camins wrote: > Excuse my stubbornness but: > I've already managed to correct the border issue, thank you. I'm now > trying

Re: [Mixxx-devel] Latenight widgetgroup borders

2015-06-26 Thread Ferran Pujol Camins
Oh, yeah view menu is the place for this. I'll give it a try asap. 2015-06-26 18:31 GMT+02:00 Be : > There already is the View menu. I am in favor of getting rid of all the > on-skin buttons and keeping all those options in the View menu. > > On 06/26/2015 10:52 AM, Ferran Pujol Camins wrote: > >

Re: [Mixxx-devel] Latenight widgetgroup borders

2015-06-26 Thread Mel Grubb
I think there are some buttons that should be available directly on the UI because they represent things that are needed during a performance. Toggling samplers on and off is one example. I want to drop down the samplers only when needed, but then I want them out of my way. For consistency, I th

Re: [Mixxx-devel] Latenight widgetgroup borders

2015-06-26 Thread Ferran Pujol Camins
Agree. The "performance-critical" layout options are already grouped together on the lower side and we don't to touch them. We are talking about removing only those buttons that appear on the upper side of the skin. They are likely to be setup once and not be changed again during a performance, so

Re: [Mixxx-devel] Latenight widgetgroup borders

2015-06-26 Thread Owen Williams
The top row of selectors is not ideal, I agree. But adding skin-specific options to app-wide menus gets painful quickly. If you add "hide crossfader" to the menu you'll also have to add support for hidden crossfader to Deere and Shade as well. Otherwise people using those skins will file bugs sayi

Re: [Mixxx-devel] Latenight widgetgroup borders

2015-06-26 Thread Ferran Pujol Camins
I can try to add the hide/show crossfader feature to deere and Shade too. Just to see if we have some kind of consensus. Would you be happy with a pull request that: 1 - Removes the top layout options buttons bar (where to place the latency bar and the clock is to be discussed, lets imagine for n

Re: [Mixxx-devel] Latenight widgetgroup borders

2015-06-26 Thread Owen Williams
If we're targeting the master branch I think that sounds ok. Definitely all the skins will have to support all of the UI switches, or else there will have to be design work for how a skin can tell Mixxx which UI switches it supports. On Fri, 2015-06-26 at 20:00 +0200, Ferran Pujol Camins wrote:

Re: [Mixxx-devel] Latenight widgetgroup borders

2015-06-26 Thread Ferran Pujol Camins
Nice, I'll start working on this as soon as I end my exams. 2015-06-26 20:11 GMT+02:00 Owen Williams : > If we're targeting the master branch I think that sounds ok. Definitely > all the skins will have to support all of the UI switches, or else there > will have to be design work for how a skin