Aha! stat.position must return a tuple of *axis* positions, not joint
positions as I thought. I guess that detail did not affect me before
because axes were interchangeable with joints in my code.
I see that stat has a new attribute called "joint_position", I guess for
consistency it might be good to rename "position" to "axis_position", but
then a lot UI would have to update there code, so scratch that!
So one more question. I have not used it in a while, but I think when using
the glade DRO widget you would select the joint number it should display,
was that actually selecting the axis index? I'll have to take a look at the
widget code I guess.
Thanks again and sorry for being a bother!
Kurt
On Fri, Apr 7, 2017 at 5:43 PM, Kurt Jacobson <kurtcjacob...@gmail.com>
wrote:
> Greetings all,
>
> I am a bit bamboozled at the moment, maybe one of you can help me out.
>
> I use a custom LCNC UI and I am trying to convert it over to support
> joint-axes so I can play with 2.8 pre. I just about got everything working
> last night for my basic XYZA config, but have hit a road block (mind
> block?) updating the DROs for a XYZB config.
>
> From what I understand with the separation of joints and axes there no
> longer needs to be a 1:1 correspondence between an axis letter and joint
> number. So even if I skip an axis (A for an XYZB config) I do not need to
> skip a join so I end up with the following axis:joint relations {x:0, Y:1,
> Z:2, B:3} Is that correct??
>
> My config starts and runs fine, but what confuses me is when I use
> self.stat.position to get a tuple with the current joint position in order
> to update my DROs the position of the B axis, which should be joint 3,
> shows up at index 4.
>
> In this case should not the position of joint 3 show up at index 3?
>
> My brain is fried, sorry if my question does not make any sense.
>
> Thanks for any insight, I'm sure the answer is simple, but I can't get at
> it.
>
> Kurt
>
>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
