Hi Bill, That sounds great.
One of the reasons for creating my application was to learn Apples new Swift language and Xcode, so that is what I’m using. I’ll have to look into QDataStream and see how I can do that with Swift. 73 /Anders > On 14 Apr 2015, at 19:23, Bill Somerville <g4...@classdesign.com> wrote: > > On 14/04/2015 17:57, Anders Östlund wrote: >> Hi, > Hi Anders, >> >> I'm writing a program that is kind of a JT-Alert alternative, but for Mac OS >> X. >> Being able to trigger a reply to a CQ from externally would be a great >> feature. >> >> I've got Mike's patch to work on r5068. Before trying to get it to work on a >> more recent commit, I just want to ask if there has been more work done on >> this already. > Yes, I am close to committing a full functioning version with a formal > message protocol that is extensible. I am adding some other messages > (outgoing from WSJT-X) that should be useful to applications like > JTAlert and yours such as status updates, WSJT-X closedown and > notification of QSOs logged. > > The protocol is binary and pretty simple, based on the Qt QDataStream > serialization capability. I am testing my changes right now after a > final clean up before check in, currently it is broken but I should have > it all working again shortly. >> >> I'd be happy to help out with testing or coding, if needed. > OK. What is your choice of implementation language and tools for your > application? I would like to have some reference code for various > platforms for usage of the message protocol. C++ with Qt I have in hand > already. >> >> 73 >> /Anders - SM0THU >> http://jt-bridge.eller.nu > 73 > Bill > G4WJS. >> >> Bill Somerville <g4wjs@...> writes: >> >>> Hi Mike, >>> >>> some more comments: >>> >>> I think it would be sensible to include the instance name in the >>> broadcast datagram as a third field. You can use the method >>> QApplication::applicationName() result as the instance name. >>> >>> There is no need to call member functions with an explicit this pointer, >>> that is not idiomatic C++, so: >>> >>> this->member(); >>> >>> becomes: >>> >>> member(); >>> >>> In MainWindow::doCallCQ() there is no need to write to the RHS decoded >>> text window, MainWindow::doubleClickOnCall() does that for you. >> [...] >> > > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
