Re: ScreenSaverEngine loading wrong view!
Re: ScreenSaverEngine loading wrong view!
- Subject: Re: ScreenSaverEngine loading wrong view!
- From: patrick <email@hidden>
- Date: Sun, 5 Feb 2006 16:28:10 -0800
Can you elaborate? I have only one view that implements
ScreenSaverView. There are a couple other views that extend
NSImageView, and these views are added to my ScreenSaverView. Even if
I comment out every bit of custom code in ScreenSaverView so that no
other views are loaded, ScreenSaverEngine still tries to load the
wrong view, making calls that are only valid with a ScreenSaverView.
Simply changing the order in which the views are compiled resolves the
problem.
If the order wasn't significant, why can you rearrange it in Xcode? My
guess is that ScreenSaverEngine is only expecting one view, though why
it wouldn't make sure it had the one that implements ScreenSaverView
is beyond me.
Patrick
On 2/4/06, Shawn Erickson <email@hidden> wrote:
> I think you have something wrong in your code...
>
> On Feb 4, 2006, at 5:48 PM, patrick wrote:
>
> > I decided to scrap everything I did, and just checkout my Xcode
> > project fresh from CVS where I know it was working. I started
> > reproducing what I had done, step by step, testing as I went along.
> > The solution to my problem was to make sure that my ScreenSaverView
> > was the *last* file in the "Compile Sources" phase of my project. If I
> > rearrange the order, placing a different view after my screen saver
> > view, I get the same problem where ScreenSaverEngine tries to load the
> > wrong view.
> >
> > I had no idea the order of files here was significant, but it really
> > seems like it shouldn't be!
> >
> > Patrick
> >
> > On 2/4/06, patrick <email@hidden> wrote:
> >> I am working on a screen saver, and all of the sudden, the
> >> ScreenSaverEngine is picking the wrong view to try and load. My
> >> screen
> >> saver has a couple of custom views which I add to my ScreenSaverView
> >> (and has been working fine until just now). I've compared all of my
> >> revisions to that latest in my CVS repository which I know was
> >> working, and even if I revert everything back, I'm still getting this
> >> problem. If I remove all of these views completely from the target
> >> (and comment out all respective lines), it works fine. I find it hard
> >> to believe that ScreenSaverEngine could get confused as to which view
> >> it should use seeing as only one of my views implements
> >> ScreenSaverView. My console log gets messages like the following when
> >> I try to load my screensaver:
> >>
> >> 2006-02-04 17:26:54.554 ScreenSaverEngine[5065] *** +[OtherImageView
> >> performGammaFade]: selector not recognized
> >> 2006-02-04 17:26:54.828 ScreenSaverEngine[5065] *** -[OtherImageView
> >> initWithFrame:isPreview:]: selector not recognized [self = 0x331870]
> >> 2006-02-04 17:26:54.877 ScreenSaverEngine[5065] *** -[OtherImageView
> >> initWithFrame:isPreview:]: selector not recognized [self = 0x338e40]
> >> 2006-02-04 17:28:06.225 System Preferences[5112] *** -[OtherImageView
> >> initWithFrame:isPreview:]: selector not recognized [self = 0x563b070]
> >>
> >> I'm at my wit's end here, and I'm hoping someone might be able to
> >> shed
> >> some insight as to why ScreenSaverEngine has gone crazy.
> >>
> >> Thanks,
> >>
> >> Patrick
> >>
> > _______________________________________________
> > 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
>
>
_______________________________________________
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