Re: Should this package be included into the NS port?

[George Plymale II]

> Yes, they will, but it’s still messy. You end up with menus that do
> absolutely nothing.

Oh, okay.

> I was hoping someone who knew would read this and give me a pointer in
> the right direction. If not I’ll get round to it at some point. :)

Oh, LOL, sorry.

> One thing to bear in mind is that the Mac port is a completely
> different code base than the NS port. The Mac port was originally
> written for the Carbon API, and the NS port for NeXTSTEP (now Cocoa
> and GNUstep).
>
> They do share some things (most notably macfont.m), but it’s not a
> given that something broken in one will be broken in the other, or
> that the code can be copied directly between them.

Right, I am aware of such differences. I just thought that perhaps some
of the Mac Port's code could be somehow imitated in the NS port to solve
this particular problem. But I can completely understand why that may
not be viable without changing a lot of parts in the NS port.

If it's not doable, that's fine. I'm just throwing suggestions out to
see what sticks.

- George Plymale II