getX and getY are unreliable when calling from touchOtherZone

[bettychang]

The getX and getY work most of the time. The only time (in my code at least) that they don't work is when I call them from the touch method in another zone... What I implemented was a timeline bar that you can scrub back and forth. When I drag the scrubber (in touchScrubber), the scrubber.getX works fine. Users can also touch the timeline directly to fast forward to that particular point and the location of the scrubber will update (with setX). In touchTimeline, the scrubber.getX then is strange.

It seems like the wrong coordinates are the actual coordinate + parent container coordinate. The hierarchy I have is the parent container -> timeline -> scrubber (3 layers).

[bettychang]

Here's a sample code illustrating the problem.

import vialab.SMT.*;
Zone parentZ;
Zone z;
Zone z2;
void setup() {
    size(displayWidth, displayHeight, P3D);  
    SMT.init(this, TouchSource.MOUSE);

    // Creates a zone
    //black
    z = new Zone("myZone", 50, 50, 100, 100);
    //grey
    z2 = new Zone("myZone2", 10, 10, 20, 20);
    parentZ = new Zone("parentZone", 0, 0, 200, 200);
    // Need to add the zone to the SMT
    SMT.add(parentZ);
    parentZ.add(z);
    z.add(z2);
}

void draw() { 
  background(79, 129, 189);
  int currX = 0;
    strokeWeight(5);
    stroke(255);
    while(currX < displayWidth){
      line(currX, 0, currX, displayHeight);
      currX += 200;
    }
    int currY = 0;
    while(currY < displayHeight){
      line(0, currY, displayWidth, currY);
      currY += 200;
    }
    stroke(0);
    strokeWeight(1);
}

void drawMyZone(){
  fill(0);
  rect(0,0,z.width, z.height);
  fill(255);
  text("1", 0, 0); 
}

void drawMyZone2(){
  fill(125);
  rect(0,0,z2.width, z2.height);
  fill(255);
  text("2", 0, 0); 
}

void drawParentZone(){
  noFill();
  strokeWeight(5);
  rect(0,0,parentZ.width, parentZ.height);
  fill(255);
  text("parent", 0, 0); 
}

void touchMyZone(){
  System.out.println("parent x: " + parentZ.getX() + " y: " + parentZ.getY());
  System.out.println("black zone x: " + z.getX() + " y: " + z.getY());
  System.out.println("grey zone x: " + z2.getX() + " y: " + z2.getY() + "<-- the unexpected line");
}

void touchMyZone2(){
  System.out.println("parent x: " + parentZ.getX() + " y: " + parentZ.getY());
  System.out.println("black zone x: " + z.getX() + " y: " + z.getY());
  System.out.println("grey zone x: " + z2.getX() + " y: " + z2.getY());
}

void touchParentZone(){
  parentZ.drag();
}

[JimWallace]

We ran into this issue this week as well - spent an hour or more narrowing down the source of the bug, and it's just crazy that Touch.x != Touch.getX(). Please address this ASAP.

[kiwistrongis]

As far as I can tell, this issue is about zones, and makes no mention of touches.

[JimWallace]

We can file a separate bug if needed then, but Touches are showing similar issues. Is it possible they are related?

[kiwistrongis]

No.