site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi all, I have an FxPlug that takes extremely small images as parameters, and I'm having trouble determining the "true" size of the source image. When I pass a 60x10 pixel image in, sometimes the FxTexture reports its width and height as 62x13, but sometimes it reports it as 60x10. If [fxTexture width] is the wrong way to get the "true" width of the texture, I would love to know the correct way. Is the problem that the image is getting resampled/antialiased before becoming a texture? Also, it would be great to be able to access the source image at full scale, even if the render is not full scale. In other words, when rendering a thumbnail, I still need all 60x10 pixels of that parameter image. As it is, it's getting downscaled to a useless 6x4 pixels. I'm now forced to implement a custom UI so I can load images from the file system. It's the only way I can reliably produce an FxTexture exactly the size of the image. I really hate reimplementing the functionality of a built-in parameter type. It's such a hacky workaround. Any advice would be appreciated! Ben _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... This email sent to site_archiver@lists.apple.com