Reply to thread

Message

It's planned down the track.

IMO I think it's best for users of the skin to have the skin update the plugins as the skin knows what is compatible not MPEI. This will be one of the down sides of moving to MPEI released packages as users will just upgrade without thinking to check if the skin supports the latest changes....but hey people want MPEI.

I understand that there is not always breaking changes so it will definitely be good for that scenario, at the end of the day there is nothing stopping power users installing MPEI packages on top of the existing libraries. The MSI installer is intelligent enough not to overwrite newer files it also has the concept of shared files which we need and MPEI does not support/recognize.

One of the main reasons we chose to embed the DLL libraries of the most popular plugins several years ago was to minimize the impact of users reporting issues with plugins that are not compatible...I think it has largely been a success, but time and again people have been asking for this (mind you only a few users and non-users!).

Anyway hopefully this issue of skin/plugin compatibility can be resolved in MPEI in the future. I may try to make the next version of the skin a FULL MPEI package with linked MPEI packages for popular plugins.

<blockquote data-quote="ltfearme" data-source="post: 1004751" data-attributes="member: 52219">It's planned down the track.&nbsp;IMO I think it's best for users of the skin to have the skin update the plugins as the skin knows what is compatible not MPEI. This will be one of the down sides of moving to MPEI released packages as users will just upgrade without thinking to check if the skin supports the latest changes....but hey people want MPEI.&nbsp;I understand that there is not always breaking changes so it will definitely be good for that scenario, at the end of the day there is nothing stopping power users installing MPEI packages on top of the existing libraries. The MSI installer is intelligent enough not to overwrite newer files it also has the concept of shared files which we need and MPEI does not support/recognize.&nbsp;One of the main reasons we chose to embed the DLL libraries of the most popular plugins several years ago was to minimize the impact of users reporting issues with plugins that are not compatible...I think it has largely been a success, but time and again people have been asking for this (mind you only a few users and non-users!).&nbsp;Anyway hopefully this issue of skin/plugin compatibility can be resolved in MPEI in the future. I may try to make the next version of the skin a FULL MPEI package with linked MPEI packages for popular plugins.</blockquote>

[QUOTE="ltfearme, post: 1004751, member: 52219"] It's planned down the track. IMO I think it's best for users of the skin to have the skin update the plugins as the skin knows what is compatible not MPEI. This will be one of the down sides of moving to MPEI released packages as users will just upgrade without thinking to check if the skin supports the latest changes....but hey people want MPEI. I understand that there is not always breaking changes so it will definitely be good for that scenario, at the end of the day there is nothing stopping power users installing MPEI packages on top of the existing libraries. The MSI installer is intelligent enough not to overwrite newer files it also has the concept of shared files which we need and MPEI does not support/recognize. One of the main reasons we chose to embed the DLL libraries of the most popular plugins several years ago was to minimize the impact of users reporting issues with plugins that are not compatible...I think it has largely been a success, but time and again people have been asking for this (mind you only a few users and non-users!). Anyway hopefully this issue of skin/plugin compatibility can be resolved in MPEI in the future. I may try to make the next version of the skin a FULL MPEI package with linked MPEI packages for popular plugins. [/QUOTE]