Open the Console and then open the Preferences. You get the following messages, both repeated several times with various panel names. Build 1217. Dec 18 09:07:11 localhost /Applications/Chimera/Navigator.app/Contents/MacOS/Navigator: objc: Both /Applications/Chimera/Navigator.app/Contents/PreferencePanes/Appearance.prefPane/Contents/MacOS/Appearance and /Applications/Chimera/Navigator.app/Contents/PreferencePanes/Navigation.prefPane/Contents/MacOS/Navigation have implementations of class PreferencePaneBase. Dec 18 09:07:11 localhost /Applications/Chimera/Navigator.app/Contents/MacOS/Navigator: objc: Using implementation from /Applications/Chimera/Navigator.app/Contents/PreferencePanes/Navigation.prefPane/Contents/MacOS/Navigation.

Yeah. I think i just need some macro fu to have the base class get a different name for each pref pane.

(Checking the validity/duplicate status of some of these older bugs) I had to actually click on a specific prefpane icon to get the messages in the Console in 2004121208 (v0.8+), but they still exist nonetheless. Is this something that can/should be fixed in the prefs rewrite for 0.9?

putting on josh's radar for the pref rewrite. smfr's macro idea is a good one.

smfr - could you be more specific about the macro fu? I couldn't get macros to do the trick...

Off the top of my head: in the taret settings for a given prefs pane: C-Flags: -DPREF_PANE_NAME=Navigation in PreferencePaneBase.h: #define PreferencePaneBase(module) PreferencePaneBase##module #define PrefBaseName PreferencePaneBase(PREF_PANE_NAME) interface PrefBaseName : ... etc. Will that work? Alternatively, can we just put the impl of PreferencePaneBase into the Camino executable, or another dylib, and have the pref panes link with that?

this doesn't need to be marked 0.9

Using build 2005052608 and Mac OS X 10.4, I am unable to reproduce this bug.

I am unable to replicate this message in the console using Nightly 20050522 on OS X 10.4.1

I'm also unable to reproduce this with a recent nightly and 10.4. Can someone try this on 10.3 or even 10.2. If it's not reproducable, I suggest resolving as FIXED.

Still here on 10.3.9....

Alright, now we're getting somehwere. So this bug is pre-10.4. Apple did something that fixed it. Is it harming anything by showing that message in the console? Or can we look past and move on? I know that's not the "best" decision, but as users slowly upgrade... What does everyone think? Is it important enough to leave open, especially considering it probably won't be fixed until 10.6 comes out! :-P

Maybe they just removed the output. It's not really an issue.

Bug 383934 will fix this.