Log in or register to post comments

New API not very intuitive

January 18, 2013 - 1:54am #1




According to the migration guide:

The API has been changed to decouple Trackables from TrackableBehaviours. A TrackableBehaviour now refers to the Trackable it represents. To access the Trackable directly (e.g. to query a Trackable’s name), the following instance fields should be used:

·                       TrackableBehaviour.Trackable

·                       ImageTargetBehaviour.ImageTarget

·                       MultiTargetBehaviour.MultiTarget

·                       MarkerBehaviour.Marker

As far as I understand there are 3 types of markers:

-Frame markers (binary markers)
-Image targets (pictures)
-Multi Targets (multiple pictures)

Then why do you call it a MarkerBehaviour and not a FrameMarkerBehaviour. Afterall, you call an ImageTarget an ImageTargetBehaviour so I don't see where that logic comes from.

Then what is a TrackableBehaviour if it comes in the same list where all the different types of markers are?







Hi Elecman,indeed the term

January 18, 2013 - 2:21am #2

Hi Elecman,

you're right, the term "Frame Marker" does not exactly match the API class "Marker" (or "MarkerBehaviour"); however the term Marker is just a "short version" of it and it is consistent with API that we have been using also in 1.5 and in native platforms (Android/iOS); 

The "TrackableBehaviour" represents the Base class/type.



Log in or register to post comments