View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012129 | MMW v4 | Framework: Skinning | public | 2014-08-02 00:53 | 2022-04-29 01:48 |
| Reporter | peke | Assigned To | |||
| Priority | none | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Target Version | 5.0.0 | ||||
| Summary | 0012129: Skinning Engine: Engine versions determine MMW Compatibility | ||||
| Description | After 0012128 is implemented in framework There is few pointer of use as it is 3 number value eg. xyz: x -> Major version Change in Skin engine like from MMW 4.x -> 5.x where skins are completely incompatible y -> New Skin structure/objects added where skin can be loaded but main parts will contain errors/artifacts (Icons, transparency, Buttons, EQ, ...) z -> Skin Tweaks/fixes where Most of Skin parts will work but there will be some occasional artifacts like in bug 0012120 where Art & Details window is black on dark skins | ||||
| Tags | todoc-dev | ||||
| Fixed in build | |||||
|
|
I wonder whether it is really needed, each addon/skin can check MM version number/build so I don't think we need another special value. |
|
|
Isn't it risk to leave skint to determine compatibility?From technical point MMW should reject Skins/addons that are incompatible. All apps that I know function that way not other way around. |
