Someone at apple is working on QC bugs (the interaction inf issue)......don't get too excited yet though

jrs's picture

Hi All,

I've had a bug report in for ages about the inf values in the interaction patch - see

https://kineme.net/forum/General/Interactionpatchbug https://kineme.net/composition/gtoledo3/BezierIterate https://kineme.net/forum/General/1024perspectiveMacOSX107108

Today I had someone at apple contact me with a request for more information about the bug.

"Why do you have four interaction patch in each of the macro? There is only one mouse, one interaction patch is enough for controlling the mouse."

I'm guessing there an intern or the like though....that or I really don't understand how the interaction patch should work?

James

franz's picture
Re: Someone at apple is working on QC bugs (the interaction ...

almost unbelievable ...

smokris's picture
Re: Someone at apple is working on QC bugs (the interaction ...

There is only one mouse, one interaction patch is enough for controlling the mouse

facepalm

gtoledo3's picture
Re: Someone at apple is working on QC bugs (the interaction ...

I've had some pretty funny replies from the Bug Reporter people from many departments at Apple over the years, but it shouldn't be taken to heart because that's just the gatekeeper.

I'm certainly not making excuses, but stepping outside of being a QC user, Interaction is a little odd in the way that multiple invocations of the object are needed on a per consumer level (somewhat inefficient?), and that it also works as a toggle setting on the Viewer.

That said, the bug reviewer focusing on that is entirely orthogonal to the actual bug, which is with the offset x/y input of the patch. Just reply back that the bug is present even with just one patch, and that one interaction patch has to be used per consumer, unless using an iterator. Keep kicking it back and eventually whoever is actually working on it will wind up fixing it or working with someone that knows how to fix it to get it done.