Even if it is a known issue, which is very well may be, developer feedback is still extremely important. Your bug could shed additional light on the problem, could show that external developers are hitting it, or could even be the first report anyone has seen. I know it's a pain, but external bug reports are very helpful.
Matt On Sep 15, 2010, at 9:48 AM, Robert Rice wrote: > Hi Matt: > > No, I didn't. I assumed it would be a known issue. > Any idea when Xcode 4 will available for general use? > > Thanks, > Bob Rice > > On Sep 15, 2010, at 12:39 PM, Matt Massicotte wrote: > >> Bob, >> >> Hopefully you've opened a bug on the IB performance you've observed. I'm >> sure the team would be very interested in a perf problem that makes IB that >> unusable. >> >> Matt >> >> On Sep 15, 2010, at 9:35 AM, Robert Rice wrote: >> >>> Hi Iain: >>> >>> As my app has grown IB became very, very slow to update my MacRuby class >>> information. Because of that I tend to avoid using IB to link outlets. >>> Instead I tag my subfields and search for then in my initialization scripts >>> using view.viewWithTag and for my new MacRuby classes I paste in the >>> superclass information rather than waiting for IB to find it. >>> >>> I think this slowness to update is a main reason for integrating IB with >>> Xcode 4. Unfortunately Xcode 4 is still only available to paid developers. >>> >>> Hope this helps. >>> >>> Bob Rice >>> >>> >>> On Sep 15, 2010, at 6:50 AM, Iain Barnett wrote: >>> >>>> On 15 Sep 2010, at 10:45, Felix Holmgren wrote: >>>> >>>>> This might not be it, but IB is in generall pretty bad at picking up >>>>> changes in code. Try Reload All Class Files from the File menu. When >>>>> you're coding Objective-C you sometimes even have to do "Read All >>>>> Class Files..." and manually point IB to the right header file. IB is >>>>> great in general, but this can be pretty frustrating." >>>> >>>> Thanks for the reply. I tried reloading the files and no change. I also >>>> tried dragging the file into the IB window but get the message "Parsed 1 >>>> source file but no classes were found or changed. I get this message even >>>> if I do change the file. >>>> >>>> This is repeatable and only happens with MacRuby, (I just tested it with a >>>> brand new project) so I don't think it's (solely) down to this kind of >>>> flakiness or I'd expect to work once in the n times I've tried it. >>>> >>>> Or maybe I am as unlucky as my lottery winnings suggest? :( >>>> >>>> Regards, >>>> Iain >>>> _______________________________________________ >>>> MacRuby-devel mailing list >>>> MacRuby-devel@lists.macosforge.org >>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >>>> >>> >>> _______________________________________________ >>> MacRuby-devel mailing list >>> MacRuby-devel@lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> >> _______________________________________________ >> MacRuby-devel mailing list >> MacRuby-devel@lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> > > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
