▲

[Torkell]

Hahahahaha!!! I have discovered the secrets of YaBB gold and I ownz you allz!!!11111!!!!1!

All your base are belong to us!

 

[Rah3D]

http://www.classicgaming.com/rotw/zerowing/

[hekla]

if the change in XMPlay 2.8 will be ok, change the panels. All things change & evoluate. Skinning XMPlay has no long history, and some 'modifications' are welcome.

Most skins are probably not to difficult to absorb the changed features. Plenty of space. If thy want use the 'old' skins, use multiple XMPlays versions. I like the look of XMPlay 1.702 best and like to skin for 2.x. My next skin for 2.7 is almost finnished & now there is comming some major chances for 2.8. That's fine by me if it's less time consuming to make the skin.

[Torkell]

All your base are belong to us

[Zarggg]

/me smacks all of you.

You fools! You know darn well that over here it's really "All your BASS are belong to us."

[Pike84]

:laugh:

[Rah3D]

Hell, yeah! :evil:

[uRRada]

The next step will be integrating player main panel
to Info window.

Cool -)))

(I am serious)

[Torkell]

He's right, y'know...

This popped up on my PC just now while I was using XMPlay:


NVidia use BASS, too:


And this is what my sound card looks like:


Is anyone worried at the amount of influence Ian must have to accomplish this?

[Ralesk]

I think those that require (only a few do, indeed, I have seen it!) retouching and it can be done without significantly changing the design, should be changed by the skin authors accordingly, and the two versions should be kept on the site.  Those that need more of a rework --- I saw we eagerly wait you's version 2s, and the old one should be still kept as in archive.  Abruptly killing out skins and thusly harming the availability of skins for people who prefer the pre 2.8 system would be ungood.

[Pike84]

Abruptly killing out skins and thusly harming the availability of skins for people who prefer the pre 2.8 system would be ungood.

..I guess, but is there really anything preferable in the earlier versions? I think XMPlay has only gotten better and better in time. Well it's no big deal, though. If some people want the old versions of skins saved, then fine. It's not like they'd take huge amounts of space or anything .

[Brightguy]

Well, what about Boggy's suggestion?

If the skin contains the old extra panels, couldn't 2.8 then just use them like 2.7 did?  If it doesn't contain the old panels, then use the new method.  That way all the work put into some of the old panels wouldn't just go to waste.  Also, people who like the old panels could use a classic 2.7 skin.

I think it's a good compromise... but is it practical?  What does everyone else think?

[Irrational86]

That'd be a little bit of bloatage

[Olego]

Being somewhat selfish and proud of XMPlay, I vote for releasing 2.703 (like 1.703--or was it?), and making new skins be a part of 3.0 package.  In addition, 3.0 would natively support CDs because, well, BASS already does.  3.0 would have DSP volume control, and all the other nifty features.  How does that sound?  
~Olego~

[Torkell]

Hmm... maybe 3.0 will also contain the fabled VERSIONINFO resource?

Seriously, it's a good idea. Changes of this magnitude should deserve a major version number change, and as such should happen for 3.0 along with native MIDI (and I mean REAL support, not fancy DirectMusic stuff) and CD support.

[Pike84]

Hmm.. Lots of different view points and opinions circling around. I have a bit mixed feelings about this, because it's basically all the same to me personally. Some people have found it confusing to have all the different panels and settings on the gui, so removing the obsolete panels completely could help in this. However, if the default skin will be changed anyway, and then it's pointed out clearly, which skins have these leftovers, then I guess it wouldn't be a problem saving the panels in the other skins..

[Ralesk]

If the skin contains the old extra panels, couldn't 2.8 then just use them like 2.7 did?  If it doesn't contain the old panels, then use the new method.  That way all the work put into some of the old panels wouldn't just go to waste.  Also, people who like the old panels could use a classic 2.7 skin.

It works JUST like that with current skins.  The only panel that remains is the Output options one, people.  You just cannot switch to the other left wide panels.  Most skins don't have a problem with that, but two skins by Rah explicitely and visibly name the other panels, therefore they sorta (only in aesthetics) break on the new version.  This is why they _need_ to be redone.  The main look of any skin is not harmed, though.
No need to panic, most skins work.  And to be honest I don't want them to be recompiled, it doesn't matter if a skin is 76k or 56k, does it?

That'd be a little bit of bloatage

There will always be people who don't like the new system, though I personally love it.  What IS the problem with versioning the skins like we already do on the skins page?
If someone is /really/ concerned about 20k of size difference (honestly, I couldn't care about that on a 1200baud modem...), then the best option is to have a skins archive of pre-2.8 skins, perhaps on the support site, and have the neutered 2.8+ skins here on the xmplay site.

Being somewhat selfish and proud of XMPlay, I vote for releasing 2.703 (like 1.703--or was it?)

'Twas 1.702.  For us it would be 2.7.12 or so, ..15 is in the 2.8 system
Ooooh, I released soooper sikrit version numbers

[Torkell]

Does that mean Ian's finally put in a VERSIONINFO resource?

[Ralesk]

I don't know, but hasn't there been manual versioning like *, + or 2.6/7 or something?

[Ian @ un4seen]

Nah, still no VERSIONINFO

Anyway... I think I'll leave the existing skins that look fine as they are, and just recompile the couple that need a little altering (ie. to remove the obsolete panel names).