So, after trying to get the NetRemote demo to work with EventGhost, I decided it would be easier / preferable to write my own network remote app that speaks to the EventGhost Network Receiver plugin. If I get it to a point where I'm happy with it, I'll open source it as a free alternative to NetRemote.
Here's the first hurdle:
I can send an event to EG that shows up in the event log as:
Net.Play['127.0.0.1', 'withoutRelease']
The problem is, it doesn't trigger the action associated with the Play event.
If I send a Play event from EGs Network Event Sender plugin, I get the same string in the event log:
Net.Play['127.0.0.1', 'withoutRelease']
But it DOES trigger the the action associated with the Play event.
Are there hidden characters at play here? I'm using the .Trim() method to get rid of any mystery characters, but still no success...
Anybody have any ideas??
Oh, by the way, the app I'm writing is in .NET 2.0 using C#. I've got a "EGSender" class to emulate the Network Sender plugin.
Any help would be appreciated
Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
Hidden Characters??
- Bitmonster
- Site Admin
- Posts: 2239
- Joined: Mon Feb 06, 2006 10:28 pm
Two ideas:
1. First try to send without the "withoutRelease" payload. This is intended for enduring events and actually some hack to the protocol that could easily break.
2. What do you use as line-ending character(s)? The protocol uses "\n" (linefeed) only, if I remember correctly. An "\r\n" might produce the problem.
1. First try to send without the "withoutRelease" payload. This is intended for enduring events and actually some hack to the protocol that could easily break.
2. What do you use as line-ending character(s)? The protocol uses "\n" (linefeed) only, if I remember correctly. An "\r\n" might produce the problem.
Please post software-related questions in the forum - PMs will only be answered, if really private, thanks!
-
LanceDrolet
- Posts: 10
- Joined: Mon Apr 02, 2007 7:58 pm
This was it! Well, in a way anyway... I was using WriteLine() to send the message. That method does the end-of-line for you (probably "\r\n"). Changed it to Write() and added the "\n" manually and it worked perfectly.Bitmonster wrote:Two ideas:
2. What do you use as line-ending character(s)? The protocol uses "\n" (linefeed) only, if I remember correctly. An "\r\n" might produce the problem.
Thanks!