Sorry for being so slow on the reply! Your comment got lost in a flood of comment spam which caused me to hold them all for manual approval :-/. I need a better system.

In the screenshot above, you can see a couple of examples. There are two “Help” menus because the system provides one and PKIThing has one in the cross platform code. Inside the help menu, there’s an “About PKIThing” item that needs to be inside the “PKIThing” menu on the mac. The “Quit” item is called “Exit” on most other platforms and is generally on the “File” menu, but needs to be in the application menu (”PKIThing”) in the screenshot on the mac. The preferences menu item is in the “Tools” menu in the sample above, but needs to be in the application menu. The border on the wxNotebook is too close to the window border. That’s good on Windows or Linux but looks weird on the Mac. The field for the file to hash in the screenshot above is not inline with the Mac conventions and should really accept drag and drop to fit in on the platform.

The use of the tabs for that UI is truthfully a little weird relative to other Mac applications. I should probably do something more like Safari’s preferences UI for the functions you see above.

There are other things I’m sure, but most all fall into areas I’d consider minor polish (similar to what I’ve listed). The major functionality is in place, and in general wxMac applications feel much better integrated than, say, Java. It’s just a lot more work with wx to get the level of polish that’s present in Cocoa by default. For some programs, though, that’s a valuable trade-off. I’ve certainly got a few in that category.

Could you possibly provide a few examples of troublesome areas to watch out for. Thanks.