Reply to thread

Message

<blockquote data-quote="MediaPortal-Bot" data-source="post: 685394" data-attributes="member: 48617">While the MPSettings values are cached, any read/write operation from it still requires a new object to be instantiated. This is normally not a problem, except that the above mentioned skinfunction causes this to happen at every render pass. MPSettings values are always cached, and thus always read from the same valuelist, so instantiation is not required everytime.Created Instance Property, and changed those read operation to use it inside PluginManager which are called by the skinfunction. Other MPSettings read operation not changed.Also removed (needless) left-over instantiation in InfoManager.<a href="http://mantis.team-mediaportal.com/view.php?id=3226" target="_blank">http://mantis.team-mediaportal.com/view.php?id=3226</a><a href="http://mantis.team-mediaportal.com/view.php?id=3226" target="_blank">Open the issue in Mantis...</a></blockquote>

[QUOTE="MediaPortal-Bot, post: 685394, member: 48617"] While the MPSettings values are cached, any read/write operation from it still requires a new object to be instantiated. This is normally not a problem, except that the above mentioned skinfunction causes this to happen at every render pass. MPSettings values are always cached, and thus always read from the same valuelist, so instantiation is not required everytime. Created Instance Property, and changed those read operation to use it inside PluginManager which are called by the skinfunction. Other MPSettings read operation not changed. Also removed (needless) left-over instantiation in InfoManager. [url]http://mantis.team-mediaportal.com/view.php?id=3226[/url] [url=http://mantis.team-mediaportal.com/view.php?id=3226]Open the issue in Mantis...[/url] [/QUOTE]

Verification