So it is basically "be aware of potential problems when doing things in different threads" which is nothing new for our app as we have some native stuff that responds to events in the Mac OS app kit thread but nothing inherent to JavaFX as far as I can see. This is what I had hoped.
Thank you. On Sun, Jun 16, 2013 at 7:19 PM, Pedro Duque Vieira <pedro.duquevie...@gmail.com> wrote: > I've grabbed my previous blog post about this subject and rewritten it to be > more up-to-date with the current state of things. > I'm sorry for the publicity but this is a far easier way to explain what > I've learned about the subject - > http://pixelduke.wordpress.com/2013/06/16/integrating-javafx-and-swing-revised/?preview=true&preview_id=542&preview_nonce=e92735d108 > > Cheers, hope this helps, > > > On Sun, Jun 16, 2013 at 8:28 AM, Robert Krüger <krue...@lesspain.de> wrote: >> >> On Sat, Jun 15, 2013 at 11:39 PM, Pedro Duque Vieira >> <pedro.duquevie...@gmail.com> wrote: >> > My biggest problems were with having 2 UI threads. >> > >> > I ran into some concurrency issues between the 2. >> > >> Meaning things that just needed extra care or things that were hard to >> work around? Could you elaborate a bit? > > > > > -- > Pedro Duque Vieira
