my bad chris, i made an entirely new project but when i loaded the comps into interface builder i was picking the old ones i sent you. wasn't paying attention to the project folder i was in. you'd think interface builder or x code would know what directory you would be loading your files from, seeing that the first thing you do is choose a root directory for your project. i feel like a jackass, i got excited as well thought there was actually a question I could answer on this board. i thought you where looking for a solution that didn't use any code. there has to be way to do it. if you can bind a comp to a IB text box and back again you should be able to do that with two qc views. hugh thats a thought maybe pass the value to a ns text box and then bind that to your other qcview ? i mean you might have to hide the text box or make 0 opacity or what ever if you don't want people to see it. hey im new to quartz im just trying to help that probably won't work, but you could try.
as per the loop back situation, its your app you got to make it so it won't break, i mean if your going to sell it. morally that is or at leaste try to cover as many basis as you can. we all know some imoral software compaines that sell us products that break, im not going to start mentioning names or anything. i know i spend more time trying to break an application i build than making it sometimes. i was un aware of this forward events thing not working right. i read documentation that said to do that so i was just trying to re iterate what i read, but clearly that is something you are allready aware of. im glad to hear that actually now i don't feel so dumb. i had tried forwarding mosue events 2 qtz in interface builder and was un able to get them to actually work with a build. gave up on it. started using OSC its not as fast as clicking forward events box but faster copying some NS event. i tried following apples documenatation it seemed pretty straight forward. havent thought about it again till today when trying to find a solution for you. On Wed, Nov 5, 2008 at 8:39 PM, Chris Wood <[EMAIL PROTECTED]> wrote: > Thanks for all the replies. > > I guess I should have mentioned at some point that I'm a network engineer > by trade, it would have saved some typing :) There are cases where the > tcp/ip loopback will get disabled, and it's possible to filter or block > loopback traffic with firewalls etc., and while it's not common, I'd rather > avoid any possible issues further down the line. > > I don't mind adding the extra code, it just seemed likely that there was > some good way to connect published ports with IB, which I'd certainly like > to know about. Guess not then? > > Dustin: just publishing the ports on both compositions like you did doesn't > actually work (it got me all exited for a minute though!) It looks like you > changed the .qtz files, but didn't reload them into the QCViews in interface > builder - the app stopped passing values as soon as I did that. > > The 'forward all events' option is actually for passing keyboard/mouse/etc > events to the composition (which would be great if it actually worked - > check the discussions in the mailing list archives if you plan to use it, > you'll need either xcode2 installed on another mac or you'll need to add a > bit of extra code to handle event forwarding manually). Oh, and you'll want > 'reply to all' for the mailing list, otherwise it just replies to only one > person (I've done that way too many times myself!) (In fact looking at it, > I've just done it now. Bugger! Copy and paste time...) > > Chris > > > On 6 Nov 2008, at 00:40, Christopher Wright wrote: > > I've considered it, but this is for use in a commercial app. It could be >>> installed literally anywhere, and I really don't want to rely on any network >>> being available - it introduces too many unknowns. Otherwise, it'd be the >>> best way by far I think. >>> >> >> >> All OS X machines will have a loopback network device (so ping 127.0.0.1will >> always work) -- if you encounter a machine without that, I'd be >> _Really_ impressed (every unix machine I've ever had (for me, the earliest >> is a 486, I'm sure many people here go much farther back) has had a >> loopback, even with no physical network interface device). >> >> According to this site -- http://forums.osxfaq.com/viewtopic.php?t=3846 -- >> loopback goes all the way back to 10.1.5/10.2, and I'm almost positive it >> goes all the way to 10.0. So your concern probably isn't too much of a real >> problem in practice. You'll be more likely to find a platform that doesn't >> support QC than you will a platform that can't do any networking (iPhone >> comes to mind ;) >> >> Just did a quick test, I made a broadcaster/receiver pair, unplugged >> ethernet, and turned off airport. continues to run as expected. This isn't >> much of a test, of course, but it at least means that the packet routing >> doesn't depend on an interface that's up. I don't have any macs without >> built-in network devices, so I can't do a complete test. >> >> To see if a machine has a loopback device, open a terminal, and run >> "ifconfig lo0". If you see this: >> >> [EMAIL PROTECTED]:~>ifconfig lo0 >> ifconfig: interface lo0 does not exist >> >> Then you've found a machine that doesn't have a loopback device -- >> someone's probably done something really nasty to it (I don't think it's a >> supported configuration at that point, and lots of things will probably act >> strangely). Otherwise, you'll see something like this: >> >> [EMAIL PROTECTED]:~>ifconfig lo0 >> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 >> inet 127.0.0.1 netmask 0xff000000 >> inet6 ::1 prefixlen 128 >> >> which means you win, things will probably work as expected. >> >> -- >> [ 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/dustin.oconnor%40gmail.com > > This email sent to [EMAIL PROTECTED] > -- Dustin O'Connor http://numedia-sci.info
_______________________________________________ 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]
