Log in or register to post comments

Tracker Manager bug

January 16, 2013 - 2:36am #1

Hello,

It seems that when the height of the tracker image is bigger than the width, the XML that gets downloaded from the Tracker Manager uses the "width" value as the height value.

Eg.: if i upload this image (http://www.farmvertical.com/wp-content/uploads/2007/10/vertical_farm_v2.jpg) and set the width to 200, then download the targets and check the XML file, it will look like this:         <ImageTarget size="150 200" name="building"/>

It seems that the value of "width" that the user enters is used for the longest side of the image. This then causes problems with the measurment and positioning.

Z.

Note: I didn't try with this specific image, but tried with few others (which I can't give ot publicly) and the problem persists. 

Tracker Manager bug

June 14, 2013 - 2:33am #7

Hi, just a quick update: this issue has now been resolved, as you can verify in the current TMS.

Thanks.

 

Thank you, I appreciate

January 16, 2013 - 5:09am #6

Thank you, I appreciate it.

Z.

Hi, we don't have a public

January 16, 2013 - 5:02am #5

Hi, we don't have a public issue tracking system, but I'm tracking this issue internally.

I will keep you up-to-date on the progress.

We've automatized the process

January 16, 2013 - 4:52am #4

We've automatized the process (our app has a CMS) and it should work without human input on this level. I'd like to stay up to date with this issue, do you have some sort of bug tracking system where I could sign up for changes?

Thank you

We've automatized the process

January 16, 2013 - 4:52am #3

We've automatized the process (our app has a CMS) and it should work without human input on this level. I'd like to stay up to date with this issue, do you have some sort of bug tracking system where I could sign up for changes?

Thank you

Hi pallzoltan, thanks for

January 16, 2013 - 4:11am #2

Hi pallzoltan, thanks for reporting this issue (which I also verified); I will check this to our engineering team;

an obvious workaround is to manually rescaling the target (editing the XML manually) so to keep the same aspect ratio, though I understand that doing it manually can be a bit inefficient.

 

 

 

Log in or register to post comments