Reply to thread

Message

<blockquote data-quote="DaBIGOne" data-source="post: 929076" data-attributes="member: 118220">I know you should use ports of 0xC000 + for user port... but 49152+ is so high it's just not funny anymore.by default EventGhost uses 1024 which is reserved, 1023 is also reserved, I think it'll be ok to use it <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />&nbsp;Well, you send messages to MediaPortal, the mediaportal core does not send MW_COPYDATA to the plugins I've tried some other messages but no succes, only messages of 0x8000+ will pass, so no WM_COPYDATA is available for plugins.&nbsp;This was the most elegant way to get this done. plus there is a whole lot more possible now <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />&nbsp;Most of the EG users are using a server (at least I do, and I know a few more) right now you can forward your event straight to the EG+ plugin. As when you use a WM or a named pipe you always need to forward your event to the EG on the HTPC and then forward that again to the plugin.Every step you can eliminate is a point of failure less, and I use the Network Event sender/receiver from EG I only made the EG plugin to make it a bit easier to forward the payloads. (without first writing a python command and stuff)</blockquote>

[QUOTE="DaBIGOne, post: 929076, member: 118220"] I know you should use ports of 0xC000 + for user port... but 49152+ is so high it's just not funny anymore. by default EventGhost uses 1024 which is reserved, 1023 is also reserved, I think it'll be ok to use it ;) Well, you send messages to MediaPortal, the mediaportal core does not send MW_COPYDATA to the plugins I've tried some other messages but no succes, only messages of 0x8000+ will pass, so no WM_COPYDATA is available for plugins. This was the most elegant way to get this done. plus there is a whole lot more possible now :) Most of the EG users are using a server (at least I do, and I know a few more) right now you can forward your event straight to the EG+ plugin. As when you use a WM or a named pipe you always need to forward your event to the EG on the HTPC and then forward that again to the plugin. Every step you can eliminate is a point of failure less, and I use the Network Event sender/receiver from EG I only made the EG plugin to make it a bit easier to forward the payloads. (without first writing a python command and stuff) [/QUOTE]

Verification