That's actually simpler. You should be able to simply start a standard thread using Runnable and use ApplicationContext.queueCallback() to post updates back to the UI (similar to SwingUtilities.invokeLater(), if you are familiar with that). These methods simply ensure that the callback is executed on the UI thread.
On Sep 29, 2010, at 2:34 AM, B.L. Zeebub wrote: > Greg Brown wrote: >> >> After giving this some thought, I don't think MessageBus is the right >> solution here. When a message is sent, the handlers are all called on the >> thread that sends the message. You could probably get something working >> with this approach, but it might not be the best way. >> >> Why not just use the native monitor support provided by the platform for >> this? Start up a plain old thread as your headless app, and have it wait() >> on some object. Your main app can call notify() on the object as needed to >> wake up the thread, and the thread can then examine the state of the >> object to determine how to proceed. >> >> Would that work? >> > > Regretably, not in this case. The headless app simply reads data from a > socket, writes it to the serial port, and then writes any response back to > the socket. It's the one that's doing all the real work - it's not driven by > the GUI. It orginally started life as a CLI running in a DOS window. The PHB > decided that this wasn't sexy enough, so I thought I'd have a go with my > first "simple" Pivot. All Pivot does is startup & shutdown the headless app > while giving the customer something to look at :( What I was trying to do > was to "flash" some LED images when the headless program received/sent data > to re-assure the customer that something waws actually happening. > > Thanks anyway > > -- > View this message in context: > http://apache-pivot-users.399431.n3.nabble.com/Heads-Up-new-Pivot-Article-tp1535411p1600606.html > Sent from the Apache Pivot - Users mailing list archive at Nabble.com.
