next »

[Cris]

Thanks a lot, Rah'Dick!

[Ian @ un4seen]

You fussy people!

Ok, instead of just using the Windows setting, I've moved it to an INI setting ("FadeBubbles"), which will default to the Windows setting. It'll eventually be added to the Options'n'Stuff.

   www.un4seen.com/stuff/xmplay.exe

i mentioned z-order before in case I didnt make sense, what I was interested in is if a skin could have a button to toggle the pos_rightoverleft between 0 and 2.  If that was possible I could use the same space for the playlist and output panel, and it would enable more minimalist skins as well   Just a thought, not sure if its practical.

[edit] also is there a way to disable the play/pause button from flashing when paused?

These can probably be arranged.

About mouseover: is there a way (as an option) to have Xmplay window(s) to become active on mouseover? Thanks! 

I don't think that's possible. If XMPlay tries to make itself active, Windows will just flash the XMPlay taskbar entry.

[amit]

this is a little off topic but i didn't think i should open a new thread as i am not talking about an official build.
i downloaded and tried to use the "xmplay.exe" Ian mentioned in his reply from 7 Jun '06 - 22:08.
the new skinning options work well but i have network problems with it. if i want to start a new http stream while already playing a stream in xmplay both xmplay and firefox freeze. i reverted to the official build (3.3.0.4) and no problems again.

Amit

[Ian @ un4seen]

if i want to start a new http stream while already playing a stream in xmplay both xmplay and firefox freeze.

You mention Firefox, so I guess you're loading a playlist from a website, eg. shoutcast.com? That seems to be fine here, so please state exactly what you're doing to make it freeze.

[Amit]

Ian , I rechecked the problem i mentioned earlier. the problem occurs  occasionally with the official version too but i have no success in locating the exact reason. i don't know yet if it is xmplay.exe , one of its plugins or  my  system cofiguration , so for now you can see it as false alarm. sorry.

Amit.

[Ian @ un4seen]

I still want those fillable slider thingies...

Here's an update to try...

   www.un4seen.com/stuff/xmplay.exe

The "fillable slider thingies" are supported via a single state "knob" bitmap, similar to the level bitmap system. Mini-mode specific knobs are also available now (knob_volume_mini.bmp & knob_balance_mini.bmp), as are position (knob_position.bmp & knob_position_mini.bmp), eq/reverb (knob_eq.bmp), amplification (knob_amp.bmp) and pan separation (knob_pansep.bmp) knobs. There are also mini-mode specific position (slider_pos_mini.bmp) and vertical (slider_vert_mini.bmp) slider options available.

Also in this update, all sliders (eg. volume/balance/position/eq/reverb/amp) can now be horizontal or vertical, automatically determined by whether the width or height of the slider is greater.

This stuff is somewhat experimental, so if you try it, please report how you get on.

[Tsorovan]

Yay. You da man. Seems to work fine! Will report back if I find any malfeasance on their part.
The nice thing is that you can have both the "fillable" sliders and the original ones, at the same time. That opens up for some pretty cool things, I'm sure.

[Maserati]

with the new exe everything seems to work normal on my wip skin.  I am interested in these fillable sliders, but would'nt that require many positions in order to appear smooth?  However I see you also say it's 'single state'.  I will have to investigate these, and delay my skin further! 

[Tsorovan]

The sliders' "resolution" is 1 px, just the same as an old slider*. It works like the old level meter, only in one direction. Create the file as the slider will look like filled, at 100%. XMPlay will then draw the slider x or y (depending on orientation) amount of pixels. For example, if your level meter is 200 px long, at 50% track length (or volume or whatever this slider it is), it'll draw pixel rows 0-99 of that particular bitmap.


*: Well, it naturally depends on the amount of steps of the thing you're changing and the length of the slider, but the maximum resolution is 1 px.

[Maserati]

ok I tried making this knob_volume into a single state fillable, by cropping out everything but the last state (100%).


however when I apply changes, it seems to work - meaning I can slide it in 1px increments, but it is showing the slider_horiz.bmp on top of it now and it covers over the little sphere. 




[EDIT]  The same thing did not happen with the knob_position.bmp because I had slider_pos.bmp hmm...

[Tsorovan]

Just delete or rename slider_horiz.bmp. Not sure what you mean by the "little sphere".

[Edit]: Ah, I see... the original post didn't have that first pic...

[Maserati]

nah I need slider_horiz.bmp for the auto_amp.  I made a mistake and it does not cover over the sphere - reffering to the round volume button.

I think the proper solution would be to add a slider_vol.bmp, as there is knob_position.bmp and slider_pos.bmp.

[Tsorovan]

Why do you need it for auto_amp though? That slider works the same if you want it to (knob_amp.bmp).

[Night Striker]

What would be cool if the volume and balance controls could follow a path instead of just horizontal or vertical but if the control was like a knob on a stereo system

[Rah'Dick]

For that, you already can use the knob technique, see my "Plastic" skin

[Ian @ un4seen]

I think the proper solution would be to add a slider_vol.bmp

Here's an update with slider_volume.bmp, slider_volume_mini.bmp, slider_balance.bmp and slider_balance_mini.bmp options to try...

   www.un4seen.com/stuff/xmplay.exe

That's a hella lot of slider/knob options now!

[Maserati]

Thanks Ian it's working great!

[Ian @ un4seen]

I've renamed the position knob files to knob_pos.bmp & knob_pos_mini.bmp, so that they follow the same convention as the sliders, as is the case with the volume and balance knobs/sliders...

   www.un4seen.com/stuff/xmplay.exe

I think I'll release a .5 update fairly soon to make these skin changes (and the other little tweaks'n'fixes) official, before starting work on the next version. Btw, I noticed it's already been over 2 years since the last default skin change, so it could be time for a change again, if anyone has any good ideas

[Tsorovan]

Another (hopefully trivial) suggestion: Text shadow (font_xshadowcolor, font_xshadowoffset) for, let's say, main/mini title and time display? It's difficult to make text on a metal/silver background gel nicely if you can't make it look "etched" using a simple text shadow.

[Brian]

I noticed it's already been over 2 years since the last default skin change, so it could be time for a change again, if anyone has any good ideas

One obvious option would be to adopt the top-rated existing skin on the support site as the default, with the author's permission, of course. The new-skins contest two years ago caused too much aggravation, and a special users' vote on existing skins would presumably more or less reflect the support-site ratings anyway.