I've been happy with the Codejock solution, but I still have to pay for it.
it and keep an open mind until I do. I don't have any need for a ribbon bar
Yikes, all they did was repackage BCGSoft! Thanks for the link. I had
hoped MS was showing some signs of creativity by developing it from
scratch, but oh well.
The CodeJock ribbon performs much better than BCGSoft, but this doc goes
out of the way to say they chose BCGSoft due to how well it meshed with
existing MFC. I think CodeJock does not mesh very well... their ribbon
for example requires a lot of jumping through hoops to set up.
-- David
I never looked at either product from a code standpoint, but GOAL #0
through GOAL #1000 in my GUI library (I hate to keep bringing this up
since I don't sell it) was to not just compile with MFC, but to work the
MFC way. That is, integrate with things like DDX/DDV and ON_COMMAND_UI
type macros, use REAL Win32 menus that really send proper messages like
WM_INITMENUPOPUP (not a custom draw window written from scratch), etc. My
goal was to do the hard work and just be able to have a developer drop it
in and go. I don't use XML because (off topic, but XML sucks) thats not
the MFC way. The MFC way is InsertItem() type calls. And I had no interest
in developing a GUI library that would require major rewrite to the app or
have a steep learning curve.
That said, strictly from the end user experience, I'd say CodeJock is
pretty smooth with very little flicker/flash. The flicker/flash in BCG is
horrid.