Reply to thread

Message

<blockquote data-quote="HomeY" data-source="post: 1064167" data-attributes="member: 68365">Yes, it does work, but I want to be able to control those 2 options.Since i work in MP Config a LOT, i'm already getting tired of the continous start of AtmoWin when i click the 'Plugins' section. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />While i can understand the benefits of such a setting, it should be configurable.With the above 2 options, it's fully configurable for the user. I'll simply run AtmoWin in my systray, keep it hidden there and that's it.AtmoLight plugin does not need to start or exit that, and i don't want the proces start/stop hooked to MP start/stop.Think about the situation where i fire up my PS3 and play a game. MP is closed, but i defo want to keep my AmbiLight on.</blockquote>

[QUOTE="HomeY, post: 1064167, member: 68365"] Yes, it does work, but I want to be able to control those 2 options. Since i work in MP Config a LOT, i'm already getting tired of the continous start of AtmoWin when i click the 'Plugins' section. ;) While i can understand the benefits of such a setting, it should be configurable. With the above 2 options, it's fully configurable for the user. I'll simply run AtmoWin in my systray, keep it hidden there and that's it. AtmoLight plugin does not need to start or exit that, and i don't want the proces start/stop hooked to MP start/stop. Think about the situation where i fire up my PS3 and play a game. MP is closed, but i defo want to keep my AmbiLight on. [/QUOTE]

Verification