> From: viesturs.la...@gmail.com
> Date: Mon, 20 Oct 2014 20:48:42 +0300
> To: emc-developers@lists.sourceforge.net
> Subject: Re: [Emc-developers] incremental change to linuxcnc's APIs for user
> interfaces
>
> 2014-10-19 16:06 GMT+03:00 Jeff Epler :
> > Las
2014-10-19 16:06 GMT+03:00 Jeff Epler :
> Last night at the Texas fest, Chris Radek, Seb Kuzminsky, and I
> brainstormed an outline of an incremental way forward, which will take
> at least two releases before the ultimate goal of transitioning from NML
> to a different IPC method.
Is it just me w
On Mon, Oct 20, 2014 at 07:53:24PM +1100, Frank Tkalcevic wrote:
> I run axis on the local machine, then remote to it using keystick.
It also *typically* works when using e.g., axis + halui or axis +
linuxcncrsh.
However, sometimes it doesn't. This leads to reports like 328 (axis +
halui, using
> (The summary of those bugs is: the serial number method for UIs to ensure
a
> message is acted upon by task simply does not work when there is not just
> one UI. No simple modification will make it work, and no one in the
project
> in 10+ years has taken the time to understand NML with the depth
On Oct 19 2014 7:06 AM, Jeff Epler wrote:
> As happens so often, the topic of linuxcnc's API for user interfaces
> came up. This time it was in the context of reported bugs like
> https://sourceforge.net/p/emc/bugs/328/ and /395/.
>
> (The summary of those bugs is: the serial number method for UIs
As happens so often, the topic of linuxcnc's API for user interfaces
came up. This time it was in the context of reported bugs like
https://sourceforge.net/p/emc/bugs/328/ and /395/.
(The summary of those bugs is: the serial number method for UIs to ensure
a message is acted upon by task simply
