Author Topic: Skin- and visual errors related to, and skinning requests for MusicBee v3  (Read 330400 times)

hiccup

  • Hero Member
  • *****
  • Posts: 9152
Well, not on purpose then. But could it perhaps be that there is either a typo, or a remaining transparency value from the skin that your skin might be based upon?

edit,

If you are using notepad++, you can find those easily doing a regex search.
Just enter: "\d+,\d+,\d+,\d+" in the search field.
Last Edit: December 10, 2015, 05:03:44 PM by hiccup

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34992
at least "Menu.DropDown.Highlight" has 0 alpha for the colour
its possible other elements are the same

hiccup

  • Hero Member
  • *****
  • Posts: 9152
id="Content[TrackDetail].ItemSeparatorLine" doesn't seem to work anymore in v3

And a minor issue that I remember also once showed up in v2 in the past.
When opening the configuration panel on a (very) dark skin, it opens with a short white 'flash'.


hiccup

  • Hero Member
  • *****
  • Posts: 9152
This looks like it might also be a glitch.

There seems to be something very wrong with that skin. When I open it with MB v2, MB crashes, and notepad opens with a very long error text.
Could there be something wrong with the images in it?

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34992
id="Content[TrackDetail].ItemSeparatorLine" doesn't seem to work anymore in v3

And a minor issue that I remember also once showed up in v2 in the past.
When opening the configuration panel on a (very) dark skin, it opens with a short white 'flash'.
the first was reported the other day and should be fixed for the next update
for the 2nd i dont see it. Which dialog window does it happen in?

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34992
<element id="Content[TrackDetail].ItemSeparatorLine" fg="xxx,xxx,xxx"/>
<element id="Content[AlbumAndTracks].ItemSeparatorLine" fg="xxx,xxx,xxx"/>
should be working now
http://www.mediafire.com/download/yg2iu46j3binune/MusicBeeDemo.zip

unzip into the musicbee application folder and run MusicBee3.exe

Bee-liever

  • Member
  • Hero Member
  • *****
  • Posts: 3871
  • MB Version: 3.6.9255 P
should be working now

Yep. All fine.

Would it be possible to have on override for the line that also appears when using a grouping header in Track Detail view.
It's currently auto-generated by MB

EDIT
or auto-generate a much darker line higher contrast line rather than the slightly darker lightly contrasting line it currently does, please
Last Edit: December 10, 2015, 11:42:44 PM by Bee-liever
MusicBee and my library - Making bee-utiful music together

Alumni

  • Sr. Member
  • ****
  • Posts: 1007
If you are using notepad++, you can find those easily doing a regex search.
Just enter: "\d+,\d+,\d+,\d+" in the search field.

Thanks for the tip! I am using Notepad++.
I did the search exactly as you said, with no results. So I can say for sure my code has no 0 alpha colors.

at least "Menu.DropDown.Highlight" has 0 alpha for the colour
its possible other elements are the same


Here's what I have for that element:

Code
<element id="Menu.DropDown.Highlight" bg="20,20,20" bdr="20,20,20" />



There seems to be something very wrong with that skin. When I open it with MB v2, MB crashes, and notepad opens with a very long error text.
Could there be something wrong with the images in it?

No idea what the problem could be... I have only tested it in v3.
Last Edit: December 11, 2015, 04:52:06 AM by Alumni

psychoadept

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10940
Now Playing List overrides appear to be working now!

These elements don't show up:

<element id="UseArtworkBorders">true</element>
<element id="Controls.FaintLine" bg="143,189,39" />


I notice that in 3.0 some buttons appear to be active which aren't, such as the Configure buttons in Player Preferences.

And can we get rid of this line in Preferences that seems to be the wrong color?

Last Edit: December 11, 2015, 04:42:04 AM by psychoadept
MusicBee Wiki
Use & improve MusicBee's documentation!

Latest patches
(Unzip and overwrite existing program files)

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34992
Here's what I have for that element:
Code
<element id="Menu.DropDown.Highlight" bg="20,20,20" bdr="20,20,20" />
can you send me the source xml file (i already have the xmlc file). Its defenitely reading that element with 0 alpha

Alumni

  • Sr. Member
  • ****
  • Posts: 1007
can you send me the source xml file (i already have the xmlc file). Its defenitely reading that element with 0 alpha


Sure, sent to you.

hiccup

  • Hero Member
  • *****
  • Posts: 9152
When opening the configuration panel on a (very) dark skin, it opens with a short white 'flash'.
for the 2nd i dont see it. Which dialog window does it happen in?

When opening the configuration panel.
But also when opening MB for a first time.
With e.g. the 'Sportura Pinstripe' skin it's very obvious here.
It's not happening always, but often enough to experience regularly.

edit:
This is the thread about the same happening on v2 before, which you were able to fix then:
http://getmusicbee.com/forum/index.php?topic=14746.msg87904#msg87904
Last Edit: December 11, 2015, 08:16:34 AM by hiccup

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34992
When opening the configuration panel.
well thats what i tested a number of times and didnt see it. Of course machines/ windows setups can differ so produce different results but unless i can reproduce it then i cant fix it. Can anyone else confirm this "white flashing" when opening dialog windows on dark skins?

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34992
Here's what I have for that element:
Code
<element id="Menu.DropDown.Highlight" bg="20,20,20" bdr="20,20,20" />
can you send me the source xml file (i already have the xmlc file). Its defenitely reading that element with 0 alpha
i had a look at the source file you sent, and compiled it. The menu element was fine with that one and couldnt reproduce the glitching i was able to reproduce before

Alumni

  • Sr. Member
  • ****
  • Posts: 1007
i had a look at the source file you sent, and compiled it. The menu element was fine with that one and couldnt reproduce the glitching i was able to reproduce before

Edit: Ok I think this might clear things up.

Code
<element id="Menu.DropDown.Highlight" bg="20,20,20" bdr="0,0,0" />

This line of code creates a border with the intended color: 0,0,0.

Code
<element id="Menu.DropDown.Highlight" bg="20,20,20" bdr="20,20,20" />

This line of code creates a border with an unintentional color: 120,120,120.
Last Edit: December 11, 2015, 11:03:38 AM by Alumni