Reply to thread

Message

<blockquote data-quote="neelex" data-source="post: 672797" data-attributes="member: 89691">Hi sa_ddam213,great to read you're well and back again. It's a crap a big amount of your development is lost <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" /> - but......interesting post from you <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />I agree with mtjoernelund, the challenge is to have a plugin - or let's say extension for MP - , that combines a status screen when using a seperate remote and a touch control screen. Just for my interest as I'm not really familiar with coding: What's the big challenge for you, sa_ddam213? Is it the above mentioned combination of 2 purposes or mainly the issues with the performance due to the limitations of the plugin variant? Generally, I would prefer to have a better performance, I think that means to use MP touch as a seperated process and not as plugin. Are there any negative impacts when not using it as a plugin inside MP? Wouldn't the focus be an issue when using an own process (asking in my dumb 'non-developer' thinking). Doesn't the touch screen need focus to work anyway, alike MP's main windows need to be focused if you want to use a remote? Sorry, if it's a silly question!I'm looking forward to the progress of the plugin in the next month! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" /> Good to have you back here!!!Cheers,Neelex</blockquote>

[QUOTE="neelex, post: 672797, member: 89691"] Hi sa_ddam213, great to read you're well and back again. It's a crap a big amount of your development is lost :( - but... ...interesting post from you ;) I agree with mtjoernelund, the challenge is to have a plugin - or let's say extension for MP - , that combines a status screen when using a seperate remote and a touch control screen. Just for my interest as I'm not really familiar with coding: What's the big challenge for you, sa_ddam213? Is it the above mentioned combination of 2 purposes or mainly the issues with the performance due to the limitations of the plugin variant? Generally, I would prefer to have a better performance, I think that means to use MP touch as a seperated process and not as plugin. Are there any negative impacts when not using it as a plugin inside MP? Wouldn't the focus be an issue when using an own process (asking in my dumb 'non-developer' thinking). Doesn't the touch screen need focus to work anyway, alike MP's main windows need to be focused if you want to use a remote? Sorry, if it's a silly question! I'm looking forward to the progress of the plugin in the next month! :thx: Good to have you back here!!! Cheers, Neelex [/QUOTE]

Verification