> Does anyone have any insight into whats causing the below crash? Its from a > quartz builder (1.4) application so maybe this is the wrong place to ask but > after searching through the mailing list archives it seems its a reasonably > common problem.
The colorspace needs to be RGB (as opposed to a single-channel space, or something inappropriate for OpenGL like CMYK or YUV), and it needs to not be DeviceRGB. I'm going to guess it's the last part of the assertion that fails (really that assertion should be split into 2 pieces so that the caller knows which piece is breaking) - perhaps the driver or display is set to a profile that happens to match deviceRGB? QuartzBuilder should probably sanitize its inputs before initializing the renderer to ensure that it won't trigger this exception. Does changing the display profile help? -- Christopher Wright christopher_wri...@apple.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
