ofZach

in case it's helpful, I have noticed odd behavior with new build system on older Xcodes but haven't seen it recently since upgrading to more recent ones-- linking errors, etc....

sure -- it def feels like we could use a friendly user facing option -- for sure this ```glm::pi()``` is going to make a lot of beginner oriented code feel...

one quick thought, I don't know if this reasonable, could we keep these constants in the ofApp class / ofApp namespace as consts, constexpressions etc -- so example and older...

can you include a simple test code and clarify more what you are seeing? it's also a little unclear what the arrow means here. (also is this on iOS, on...

thanks roy! one thing I was thinking about is that it's maybe not a bug if you've added points already to the polyline and you want to append a curve....

would this work ``` line.addVertex(p2); // appending a curve line.curveTo(p1); line.curveTo(p2); line.curveTo(p3); line.curveTo(p4); ``` I think it's almost a kind of semantic question of if "curveTo" includes or doesn't include...

I think some ways to think about core addons are: (a) does this add-on help other people who are making addons (ie, can you build off of it?). (b) does...

I think it's good to replace these but I am a little worried about tons of code breaking by just removing these rather than depreciating them.... I know I personally...

or alternatively, instead of just putting them all in a #if defined(OF_USE_LEGACY_MACROS) block, still allowing them but adding deprecation warning at the usage level if OF_USE_LEGACY_MACROS is not defined.... it...

a potential fix is to call reallocate the OES texture and pass it on on resume: ``` void ofxARCore::reloadTexture() { GLuint texId = setupTexture(); JNIEnv *env = ofGetJNIEnv(); jmethodID javaSetupMethod...