I would subclass the view but that would still involve writing my
own -setCompositionRenderer, and generally much messing around with
private APIs (e.g. I would like to subclass QCImageView too), so I
decided to create a clone that only inherits from NSView,
NSImageView etc. so that nothing breaks unexpectedly.
With that last bit, I'd venture to say that those who know aren't
going to tell. At least, that's been my experience :)
Does the regular parameter view now handle this, and if so, how?
What are the spacing and layout constants used?
Do you also set copiesOnScroll? How do you handle isOpaque?
Are there any non-public methods that related classes like QCView
expect a parameter view to implement, that I would need to duplicate
too?
Most, if not all, of these can be obtained by creating an object, and
then interrogating it. I'd personally tilt towards always returning
NO for isOpaque (since I love transparency :), but the others I've not
played with enough to know. That last one will be a bit difficult
though.... that might require some exploration.
I realise many of these are best practice requests for creating
custom views and scroll views in general, but it would help if I
could get as close as possible to the way QCCompositionParameterView
implements things.
Again, to get as close as possible, interrogate what you're trying to
duplicate. Use GDB if you're truly adventurous.
--
[ christopher wright ]
[EMAIL PROTECTED]
http://kineme.net/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
