Remote UIs are the preferred way with QtQuickVcp since you can work with a single client application.
If you want a UI as "local UI" you need to compile a new client application. This only necessary when you develop a new custom UI. euerka writes: > Hi Alex, > > I tried your two examples, they all work well except segment failed when > try to open nc files from client side(computer side). > By the way, now machineface or Cetus all are download into host side(BBB > side), so it shows as remoteUI. > How to active localUI? > Thanks! > > -chengxi > On Monday, 17 October 2016 14:28:56 UTC+8, Alexander Rössler wrote: >> >> Hi chengxi, >> >> Sorry for the inconvenience. The "ensure_mklauncher" error was a typo >> that I have fixed recently. >> >> Please update Machinekit (sudo apt-get update, sudo apt-get install >> machinekit) and try a very simple demo application to verify that it >> works: >> https://github.com/machinekoder/anddemo >> >> The next step is to run the mkwrapper-sim demo: >> https://github.com/machinekoder/mkwrapper-sim >> >> Then you can go ahead and try to the other Machinetalk configurations. >> >> euerka writes: >> >> > Then I tried: >> > >> > debian@arm:~/anddemo$ mklauncher . --debug >> >> >> > >> > the result shows in (http://pastebin.com/27cxWGTV). >> > >> > Any idea? >> > >> > -chengxi >> >> >> -- >> Alexander >> -- Alexander -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
