Re: possible nib corruption?
Re: possible nib corruption?
- Subject: Re: possible nib corruption?
- From: Guy English <email@hidden>
- Date: Fri, 3 Dec 2004 22:49:37 -0500
Uh ... wierd. :) Well I guess it's fixed now though. Did you save the
old NIB file? Maybe it could help you work out what happened?
On Fri, 3 Dec 2004 18:39:01 -0500, Matthew
<email@hidden> wrote:
> Any by the way, for some closure, deleting the instantiated Controller,
> reinstantiating it, and then redoing all of the outlets/connections did
> fix the problem in case you were wondering. It wasn't a ton of work,
> but wasn't desirable either.
>
>
>
>
> On Dec 3, 2004, at 5:18 PM, Matthew wrote:
>
> > Guy,
> >
> > It's definitely a progress indicator. here's the output from logging
> > it: <NSProgressIndicator: 0x331ef0>
> >
> > Also, I don't call setThreadedAnimation on it. I just have a start
> > point and a stop point and use the animation calls to handle
> > those...again, those work in my 2 minute fresh-project example, but
> > not in my other project.
> >
> >
> > On Dec 3, 2004, at 5:09 PM, Guy English wrote:
> >
> >> Hey,
> >>
> >> Do you call - (void) setThreadedAnimation on it? If you start
> >> doing a ton of work and don't tell it to thread the animation then
> >> you'll never see it spin.
> >>
> >> Otherwise try: NSLog( @"Indicator: %@", indicator" ); and make
> >> sure it's the object you think it is.
> >>
> >>
> >> Guy
> >>
> >> On Fri, 3 Dec 2004 16:53:21 -0500, Matthew
> >> <email@hidden> wrote:
> >>> Hello all,
> >>>
> >>> In my project, I've added a simple indeterminate progress indicator
> >>> NSProgressIndicator indicator, set it up correctly to be
> >>> indetermiante,
> >>> etc. and called [indicator startAnimation:nil]; but it will not spin.
> >>>
> >>> I opened up a fresh new XCode Project and added one to a fresh window
> >>> and threw on a button to start and stop it, and it works fine...I'm
> >>> not
> >>> doing anything differently here than in my other project.
> >>>
> >>> I'm certain that the startAnimate: is getting called, all outlets are
> >>> set up correctly, etc. I've tried to manually 'repair' it by taking
> >>> it
> >>> off, putting it back on saving, restarting XCode, etc. but it isn't
> >>> working no matter what.
> >>>
> >>> What should a person do when these odd ball things happen other than
> >>> reinstantiating the controller?
> >>>
> >>> Matthew
> >>>
> >>> _______________________________________________
> >>> Do not post admin requests to the list. They will be ignored.
> >>> Cocoa-dev mailing list (email@hidden)
> >>> Help/Unsubscribe/Update your Subscription:
> >>> email@hidden
> >>>
> >>> This email sent to email@hidden
> >>>
> >> _______________________________________________
> >> Do not post admin requests to the list. They will be ignored.
> >> Cocoa-dev mailing list (email@hidden)
> >> Help/Unsubscribe/Update your Subscription:
> >> email@hidden
> >>
> >> This email sent to email@hidden
> >>
> >
> > _______________________________________________
> > Do not post admin requests to the list. They will be ignored.
> > Cocoa-dev mailing list (email@hidden)
> > Help/Unsubscribe/Update your Subscription:
> > email@hidden
> >
> > This email sent to email@hidden
> >
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden