Hi all,
does ne1 have the kindness to point me the right direction to have an
INTERACTION port on a custom Consumer Patch.
I haven't been able to find any info on that ....
thanks in advance
with official api, you're done (there's no way to add an interaction port to a QCPlugIn patch). With the skankysdk, you must ensure that your patch is a subclass of QCRenderingPatch (not just QCPatch) -- this should give you an interaction port automatically.
thxx for the fast reply.
Unfortunately, my patch is official....
Do you still maintain the skanky SDK ?
Is there a way to port my official patch to skanky patch ?
That would be much appreciated.
btw- as far as i remember, you had a very neat method for setting ports default values... i'm also greatly interested in that feature ....
we maintain the skankysdk still (it's our primary development platform, after all :), and in fact just performed a major overhaul for 10.6 (to help us develop on both 10.5 and 10.6 in detail, without every project drifting out of sync with the others). However, we've also added a number of in-house things that make it generally less useful for 3rd party (4th party?) developers (as in, it doesn't work out of the box, and requires some specialized build scripts), so we don't really intend to make it public.
Porting between skankysdk and official api is mostly simple (there are exact parallels between the official api methods and the skankysdk methods).
We don't have all the propery/@dynamic/attribute dictionary stuff that the official api does, which is how ports are normally configured -- that's unfortunately one aspect that doesn't cross over very well, if at all (skankysdk ports are actual objects, while official-api ports are lame string descriptors -- without access to actual objects, it's tricky to do mundane things like setting max/min/default values, etc).
May i download the skanky sdk ?
- i don't wanna seem pressurizing you, but i got pretty excited, esp by the easy defaults !
( i promise i won't send you tons of email questions ... ,):
EDIT: found it ! i guess 0.5 is up to date ...
EDIT2: no, it's from 2007 .... ;(
yeah, 0.5 was the last public release -- it's missing all the image stuff from Leopard (it was changed from Tiger, and we hadn't reversed it at that point), and has nothing from 10.6. Our in-house version has all 10.5 and 10.6 stuff.
official api, or skankysdk?
with official api, you're done (there's no way to add an interaction port to a QCPlugIn patch). With the skankysdk, you must ensure that your patch is a subclass of QCRenderingPatch (not just QCPatch) -- this should give you an interaction port automatically.
thxx for the fast reply. Unfortunately, my patch is official.... Do you still maintain the skanky SDK ? Is there a way to port my official patch to skanky patch ?
That would be much appreciated.
btw- as far as i remember, you had a very neat method for setting ports default values... i'm also greatly interested in that feature ....
we maintain the skankysdk still (it's our primary development platform, after all :), and in fact just performed a major overhaul for 10.6 (to help us develop on both 10.5 and 10.6 in detail, without every project drifting out of sync with the others). However, we've also added a number of in-house things that make it generally less useful for 3rd party (4th party?) developers (as in, it doesn't work out of the box, and requires some specialized build scripts), so we don't really intend to make it public.
Porting between skankysdk and official api is mostly simple (there are exact parallels between the official api methods and the skankysdk methods).
We don't have all the propery/@dynamic/attribute dictionary stuff that the official api does, which is how ports are normally configured -- that's unfortunately one aspect that doesn't cross over very well, if at all (skankysdk ports are actual objects, while official-api ports are lame string descriptors -- without access to actual objects, it's tricky to do mundane things like setting max/min/default values, etc).
May i download the skanky sdk ? - i don't wanna seem pressurizing you, but i got pretty excited, esp by the easy defaults ! ( i promise i won't send you tons of email questions ... ,):
EDIT: found it ! i guess 0.5 is up to date ... EDIT2: no, it's from 2007 .... ;(
yeah, 0.5 was the last public release -- it's missing all the image stuff from Leopard (it was changed from Tiger, and we hadn't reversed it at that point), and has nothing from 10.6. Our in-house version has all 10.5 and 10.6 stuff.