Shoutbox

New Skins [solved] - Printable Version

-Shoutbox (https://shoutbox.menthix.net)
+-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58)
+--- Forum: Messenger Plus! for Live Messenger (/forumdisplay.php?fid=4)
+---- Forum: Skinning (/forumdisplay.php?fid=41)
+----- Thread: New Skins [solved] (/showthread.php?tid=88314)
New Skins [solved] by blessedguy on 01-11-2009 at 07:59 PM

Ok, so the new Plus! is released and we discovered that the RC is also the Final version.
So, first of all, in our skins, how should the new messenger version be described?

For WLM2009 14.0.8050.1202 would be:
"Major: 14
Minor: 0
Build: 8050
Revision: 1202" ?
Also, should we include the build and revision numbers?

RE: New Skins by Menthix on 01-11-2009 at 10:39 PM

quote:
Originally posted by blessedguy
For WLM2009 14.0.8050.1202 would be:
"Major: 14
Minor: 0
Build: 8050
Revision: 1202" ?
Correct.

Just specifying Major, Minor, Build will be enough, you could leave out the build too, but that can give unexpected results when they release a new build.
RE: New Skins by blessedguy on 01-11-2009 at 11:13 PM

Oh, and one thing, when resources are extracted, and the extraction log shows up, it shows and incorrect version of messenger:

"Windows Live Messenger version:  14.0.1202.8050"

while the correct would be

"Windows Live Messenger version:  14.0.8050.1202"

RE: New Skins by mynetx on 01-12-2009 at 12:39 PM

quote:
Originally posted by blessedguy
it shows and incorrect version of messenger
Similar stuff to this has been part of some discussions. It really depends on if you prefer Major.Minor.Build.Revision (like 14.0.8050.1202, Microsoft prefers this way) or vice-versa (like 4.79.0.353, Patchou prefers Major.Minor.Revision.Build).

For what you should use in skins, I personally use
XML code:
        <Compatibility>
            <MsgVersion Major="14" Minor="0" Build="8050"/>
        </Compatibility>
Just don't omit both Build and Revision as MS might release an incompatible update.
RE: New Skins by blessedguy on 01-12-2009 at 12:44 PM

Thanks mynetx =)
And I've changed cthe compatibility tag yesterday ;p