For the project I wish to complete, TCP/IP connectivity is really the only missing feature.
I can pass data both directions from the TNI DLL (not tested, but I did see both a library call and a message posting operation).
To make the next part work, I need to be able to open a TCP/IP socket connection (two actually) to JMRI and pass messages back and forth between Trainz and JMRI.
The protocol I need to implement is a line by line text protocol, so the ultimate would be for me to be able to write a string to a socket whenever I need to pass data to JMRI and to get some kind of a notification or event every time a line is received from JMRI.
On the other hand, a less "automatic" functionality is fine assuming that there is a polling functionality. I can write the code to send strings out and parse inbound strings for newlines. In this case, I might either try to implement the receiving functionality as a thread or use a post message with delay loop to check for new messages depending on what features are implemented.
--Grant
I can pass data both directions from the TNI DLL (not tested, but I did see both a library call and a message posting operation).
To make the next part work, I need to be able to open a TCP/IP socket connection (two actually) to JMRI and pass messages back and forth between Trainz and JMRI.
The protocol I need to implement is a line by line text protocol, so the ultimate would be for me to be able to write a string to a socket whenever I need to pass data to JMRI and to get some kind of a notification or event every time a line is received from JMRI.
On the other hand, a less "automatic" functionality is fine assuming that there is a polling functionality. I can write the code to send strings out and parse inbound strings for newlines. In this case, I might either try to implement the receiving functionality as a thread or use a post message with delay loop to check for new messages depending on what features are implemented.
--Grant