Welcome to the MacNN Forums.

3R1C · May 9, 2002, 08:14 AM

Does anyone have any code laying around which implements OADockStatusItem? I've looked at the header but got little help. I think I need to initialize it with a badge icon, a number, and a text color but don't know how.

3R1C · May 9, 2002, 11:48 PM

Where is the Rickster when you need him? Just kidding.

Rickster · May 10, 2002, 01:28 AM

In San Jose, and running an operating system that OmniAppKit currently won't build on. Will get to this question when I return...

speirsfr · May 10, 2002, 03:49 AM

I don't know about text colour, but to get a count and icon you could do something like this:

<BLOCKQUOTE>code:<HR><pre>
OADockStatusItem *dockItem = [[OADockStatusItem alloc] initWithIcon: [NSImage imageNamed: @"iconBadge"]];
[dockItem setCount: 10];
[dockItem show];
[/code]

Currently, I find it annoying that you can't put an arbitrary string in the badge as I want to put a string like "2:10" in the badge, but hey.

HTH,
Fraser

Rickster · May 14, 2002, 07:10 PM

Okay, looks like Fraser answered for me. Good.

The current version of OADockStatusItem was (re)written with a very specific purpose in mind... we didn't want to have generalized (and thus untested code) begin added close to the OmniWeb 4.1 release. Of course, you're quite welcome to extend it yourself and submit changes back to us...

3R1C · May 15, 2002, 07:09 PM

I've managed to get OADockStatusItem to work. I've also replaced the left center and right tiffs of the badge background in the framework to use a 'Mail.app like' red badge. My only two think left I'd like to modify, are the text color of the number and the icons position. I'd like the text to be white and the badge to centered. I guess I could modify the framework to reflect these changes, as I did the badge, but this seems to be 'cheating' sort of. How does one go about telling OADockStatusItem to use MY tiffs and MY text color and MY badge position? I have no doubt this is probably a very easy thing to do, I just have no idea how to do it.

speirsfr · May 17, 2002, 05:40 AM

Originally posted by Rickster:
Okay, looks like Fraser answered for me. Good.

The current version of OADockStatusItem was (re)written with a very specific purpose in mind... we didn't want to have generalized (and thus untested code) begin added close to the OmniWeb 4.1 release. Of course, you're quite welcome to extend it yourself and submit changes back to us...

I was having a look at this today, but it seems that OmniAppKit won't compile with the new Proejct Builder release:

<BLOCKQUOTE>code:<HR><pre>#define NSSTRINGIFY(name) @ ## '"' ## name ## '"'
[/code]

seems to barf:

<BLOCKQUOTE>code:<HR><pre>
Widgets.subproj/OAAquaButton.m:167: illegal expression, found `@'
cpp-precomp: warning: errors during smart preprocessing, retrying in basic mode
Widgets.subproj/OAAquaButton.m:167: invalid identifier `@'
Widgets.subproj/OAAquaButton.m:167: `@' undeclared here (not in a function)
Widgets.subproj/OAAquaButton.m:167: parse error before character constant
[/code]

Rickster · May 17, 2002, 05:08 PM

The NSSTRINGIFY problem only occurs if you're using the gcc3 compiler. Switch back to gcc 2.95 and you'll be fine.

Remember, you should only use the beta gcc3 compiler in the April tools for evaluation purposes, not for shipping code -- it's not just a good idea, it's stipulated by the License Agreement on the Developer Tools.

You can pretty easily work around the problem to get the Omni frameworks to build, though... just manually expand the NSSTRINGIFY macro in all the files that use it.

[edit: corrected myself about code releases to fix the problem]

[ 05-17-2002: Message edited by: Rickster ]

speirsfr · May 18, 2002, 02:02 AM

Hmmm...I thought you had to explicitly choose GCC3 in a build setting, which I didn't do. I wasn't intending to use GCC3, so I'll check that again.....

Fraser