Marcel Ruegenberg

I think this might remove the wrong object in case of multiple payments. You'd have to reverse the iteration (see `removePurchasesChangedCallbackWithContext`) to do this correctly. A better way is probably...

Unfortunately, I don't have time at the moment, and it's not really a priority for me... However, I do gladly accept pull requests!

Unfortunately, I currently don't have a use case for IAPManager on OS X. In principle, it should actually work without modification, since the dependencies (CoreFoundation and StoreKit) are both available...

Please try the [osx-support](https://github.com/mruegenberg/IAPManager/tree/osx-support) branch. It compiles, and should work in principle, but I can't really test it right now.

Closing this for now. OS X support is in the main branch in included in version 0.2.3. If there are any problems with OS X, please open a new issue.

Haven't tested it yet. I didn't know about the receipt validation problem, so I guess there is no OS X support after all :-( Unfortunately, I have very little time...

Hey, can't say much about this except that I think you're right on all points :)

It works when doing ``` bool didUseNormalizedTexCoords = ofGetUsingNormalizedTexCoords(); ofDisableNormalizedTexCoords(); mClient.draw(50, 50); if(didUseNormalizedTexCoords) ofEnableNormalizedTexCoords(); ``` This feels kind of hacky though, and doesn't really work for code that expects normalized...

I "solved" it by rendering the Syphon result to a FBO first. I then use its texture where normalized tx coords are required. Not very efficient, but seems like a...

Thanks for the super-quick reply! The one in 0.9.1 works as it should.