Reply to thread

Message

<blockquote data-quote="Inker" data-source="post: 84174" data-attributes="member: 10541">Well, there have been talks about automatically using the B2 xml if no skin specific implementation can be found, however this has some downsides as well, such as graphics not found, ackward positions, calls for fonts that havent been created, etc. and so it just wasnt done (yet?). While the issues mentioned above arent a certainty and it probably would somewhat work in 75% of the cases, I'm not sure its a bad strategy to make the user aware that they need to take some manual action because what they are trying to do is (and cannot be) unsupported. Otherwise the user won't even know whats going on and will just assume there is a bug in the plugin or MP itself.Now perhaps one could spice up the error about the missing xml file a bit, suggesting the user may (at his own risk) try to copy the corresponding file from the blue two folder if they are using a third party skin.Just my thoughts.</blockquote>

[QUOTE="Inker, post: 84174, member: 10541"] Well, there have been talks about automatically using the B2 xml if no skin specific implementation can be found, however this has some downsides as well, such as graphics not found, ackward positions, calls for fonts that havent been created, etc. and so it just wasnt done (yet?). While the issues mentioned above arent a certainty and it probably would somewhat work in 75% of the cases, I'm not sure its a bad strategy to make the user aware that they need to take some manual action because what they are trying to do is (and cannot be) unsupported. Otherwise the user won't even know whats going on and will just assume there is a bug in the plugin or MP itself. Now perhaps one could spice up the error about the missing xml file a bit, suggesting the user may (at his own risk) try to copy the corresponding file from the blue two folder if they are using a third party skin. Just my thoughts. [/QUOTE]

Verification