I just added the <Style> hack to the <WNumber*> groups too. RJ Russell Ryan wrote: > Hey jus, > > First some errata about the skin format: > > You can now customize the color that a beat mark highlights to as it > passes over the center mark. It was previously hardcoded to white. > > <Visual> > .. > <BeatHighlightColor>#000000</BeatHighlightColor> > .. > </Visual> > > > I responded to what I can answer inline: > > jus wrote: > >> Hello devs, >> any news on my questions? >> Would love to finish the skins for v1.8 , got some spare time >> left this week. >> >> jus >> >> >>> How many states need a rotary button (i.e. Master volume )? Outline >>> skin has 40 , LateNight currently 27 ( 270 degree rotation). >>> >>> >>> > Not sure what is best -- in general, more states means higher precision > available to the user. Albert has a tool that given a background and the > knob will automatically generate as many rotations steps as you want > between a given set of angles. > >>> Some feedback for devs on making skins with the current code in trunk: >>> >>> Working with text is difficult >>> * Text renders different in Mac/Win/Lin (i.e. Fondsize 18 is big in >>> WIN/LIN but much smaller in Mac ) >>> * some Fondsizes are hardcoded and not alterable ( i.e the <Text> key >>> = Track information display ) >>> > OK it looks like you could really use this to give the skins some final > polish -- as a hold over until we rewrite the skinning system to be much > better, I'm enabling a special <Style></Style> block on both the <Label> > and <Text> groups. You will need to grab the latest version of trunk. > Whatever you stick inside that tag will be set as the widget's style > sheet. To tweak the font ,font size, etc. see the Qt style sheet > reference here: > > http://doc.trolltech.com/4.5/stylesheet.html > > To set the font to "Droid Sans Mono", 14px I would do the following: > > <Text> > ... > <Style>font: "Droid Sans Mono"; font-size: 14px;</Style> > ... > </Text> > > I'm not sure about the problem with fontsize 18 being different on > Windows/Linux/Mac. Perhaps you should use 'em' instead of 'px' in the > stylesheet. > > You will need to use a font name that will be found on all the > platforms. I'm not sure if you can specify a series of fonts to try in > the font: section. > > Please don't set the text or background colors using the style sheet, > since the skin's color scheme will not be taken into account. Use the > <FgColor> and <BgColor> tags for that (sorry). > > >>> * The <Text> key (Track information display) should not have (at >>> least as option) artistname & trackname tied together. Better make >>> separate keys for artistname & trackname. >>> >>> > We can't really change this before 1.8.0 because there isn't enough time. > > >>> Buttons >>> * Sync button should permanent lit when sync track is active >>> > The sync button isn't a mode, it happens once when you click it. > > >>> * Loop button should permanent lit when loop is active >>> > Yup, there's a bug open for this. Not sure if the fix will make it into > 1.8.0 though. > >>> * Pitch Reset button is missing (works currently only via shortcut?) >>> >>> > Yes, I don't think there's a way to make a button for this. > Right-clicking the pitch slider will reset the pitch. > >>> Background colors >>> * What are the background colors on <Visual> ( Waveform display) >>> and <Overview> (Waveform overview) good for? Let the skin`s >>> background handle that, may also save CPU power. >>> > The background of the waveform is a gradient (you can barely see it). > Unfortunately if we don't set a background, then it doesn't default to > something sane.. its just white. > >>> * Same for all the text`background colors. >>> > Qt supports auto-inheriting the palette of your parent for every widget. > Unfortunately none of our widgets do this, and set the > foreground/background color manually. This isn't something that we can > fix before 1.8.0 -- :-/. > >>> Markers for loops & cues >>> * If the skin is using a pixmap for a custom marker( a feature i >>> really like) , the default marker are shown beneath. Better don`t >>> show them at all. >>> > > Do you mean the line, the triangles, or both? If a custom pixmap is > specified it does make sense to disable them all together. > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel >
------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
