> Am 21.07.2016 um 20:04 schrieb Klemen Živkovič <[email protected]>:
> 
> That's wonderful I will try this immediatelly. :)

there's more wonderful stuff in store over at the google protobuf docs site - 
you'll save a lot of time working through this first: 
https://developers.google.com/protocol-buffers/docs/cpptutorial

there's a Python version as well, which helps a lot for quick tests. You want 
the protobuf version2 docs.

> 
> Thanks
> 
> On Thu, Jul 21, 2016 at 3:00 PM, Michael Haberler <[email protected]> wrote:
> 
> > Am 21.07.2016 um 14:35 schrieb Klemen Zhivko <[email protected]>:
> >
> > Hi everybody,
> >
> > I am using mk and mkwrapper I am getting below data on client.
> > If I use:
> > y = contReturned.getEmcStatusMotion().getActualPosition().getY();
> >
> > to retrieve value of Y I always get 0.0 from such incremental updates - Is 
> > there a programatic way of knowing that for example Y actualPosition was 
> > not even inclulded in data so asking for:
> > contReturned.getEmcStatusMotion().getActualPosition().getY()
> > doesn't make sense?
> >
> > I mean - I could serialize this to string and try regularExpressions on 
> > actual position and y, but this not efficient aproach. What is correct 
> > aproach to know what fields to extract from MT_EMCSTAT_INCREMENTAL_UPDATE  
> > packages?
> > On my first try it seems like NULL values could solve this - so my idea was 
> > for example that if actualposition y is not in data than NULL should be 
> > returned. Base on that client could now that thi data was actually not 
> > present in package.
> > Comments please.
> 
> See the protobuf documentation for a protobuf question, here: how do 
> determine if a field is present
> 
> https://developers.google.com/protocol-buffers/docs/reference/cpp-generated#fields
>   - see has_* methods.
> 
> 
> >
> >
> > Serialization of incremental data on client that I get:
> >
> > type: MT_EMCSTAT_INCREMENTAL_UPDATE
> > emc_status_motion {
> >   active_queue: 0
> >   actual_position {
> >     x: -1.8890249633789062
> >   }
> >   axis {
> >     index: 0
> >     input: -1.8890249633789062
> >     output: -1.8900000000000032
> >   }
> >   distance_to_go: 1.1079999999999997
> >   dtg {
> >     x: -1.1079999999999968
> >   }
> >   id: 336
> >   joint_actual_position {
> >     x: -1.8890249633789062
> >   }
> >   joint_position {
> >     x: -1.8900000000000032
> >   }
> >   motion_line: 336
> >   position {
> >     x: -1.8920000000000032
> >   }
> > }
> >
> > --
> > 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.
> 
> 

-- 
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.

Reply via email to