03-09-2014, 02:37 PM
I encounter another conflict with CORE handling suite, I think. This time it is the HitTest.
I acquire sHitTest myself and can't get any hit on path, is this a conflict with CORE hit test?.
So, I use CORE hit test as follow:
bool isValid = this->__artblue.cursorHitData(hitData,
//hdi::core::SegPointHitRequest,
hdi::core::FillHitRequest,
7.0);
if (isValid) {
if (hitData.hit()) {
hitType = hitData.hitType();
seg = hitData.segPointIndex(); // -1 if not SegPointHit, SegInPointHit, or SegOutPointHit
t = hitData.tValue();
hitPoint = hitData.point();
//bz = hitData.bezier();
}
isValid = false;
}
}
With only FillHitRequest enabled, CORE reports hits on everything (segment, points, handle in/out).
With only SegPointHitRequest enabled, CORE reports hits segment but never anchor hit.
Am I correct?
Vincent
I acquire sHitTest myself and can't get any hit on path, is this a conflict with CORE hit test?.
So, I use CORE hit test as follow:
bool isValid = this->__artblue.cursorHitData(hitData,
//hdi::core::SegPointHitRequest,
hdi::core::FillHitRequest,
7.0);
if (isValid) {
if (hitData.hit()) {
hitType = hitData.hitType();
seg = hitData.segPointIndex(); // -1 if not SegPointHit, SegInPointHit, or SegOutPointHit
t = hitData.tValue();
hitPoint = hitData.point();
//bz = hitData.bezier();
}
isValid = false;
}
}
With only FillHitRequest enabled, CORE reports hits on everything (segment, points, handle in/out).
With only SegPointHitRequest enabled, CORE reports hits segment but never anchor hit.
Am I correct?
Vincent