Documentation

I've just come across another gem, which I'll share with you:

CXTTabCtrlBaseEx

CXTTabCtrlBaseEx is a CXTTabCtrlBase derived class. It is used to create a CXTTabCtrlBaseEx class object.

It's certainly a concise statement, but not a single word adds any understanding to the purpose of this class, how to use it, nor its advantages over CXTTabCtrlBase (the documentation of which is no better)!

This sort of thing would be acceptable for free software, but when there's a price tag, you expect better.  I've seen much better documentation for free software from CodeProject.  In fact, I was only able to understand how to use CXTResizeDialog after reading this article:

http://www.codeguru.com/Cpp/W-D/dislog/resizabledialogs/arti cle.php/c1925/

I was initially very frustrated with the documentation. To the point that I sent tons of e-mails and suggestions to the support team. This was in the first week of trying to learn how to apply it to my application.

I also made the same suggestion that samples should be indexed based on features that they use to make finding relevant code easier.

In my app menus and toolbars are completely dynamic and defined via configuration scripts. So none of the standard functions of loading them from existing resources applied. Also, the initialization of these could not be done during window creation as in all the samples because the script engines including VBA are not initialized until some time after the creation of the window. None of the documentation was relevant even at hinting where I should start looking much less provide the relevant information.

However, after the initial frustration and reluctance to dive into the XTP source (headers and source files) I finally did dive into these. What I discovered is that if you are willing and able to work with the source, frustration will diminish enourmously.

The toolkit is well architected and easy reading (as easy as heavily modal, event driven application can be). The added advantage is to be able to single step and break point live code to get a better understanding of how it works.

I also discovered that the functionality I needed to use is way out of the beaten path and was either missing altogher or had some "omissions" or bugs which were easy to fix once I got familiar with the layout of the source files. My version now has some tweaks that allow completly dynamic menus and toolbars which can also be customized. The added functions were quickly built from existing functions as a starting point with a little experimentation.

I no longer refer to the documentation except for very rare circumstances such as finding an Enum that I know is listed there, but not much more. I go directly to the header files and source files to get my answers.

In the end I was able to get all the functionality working in my non-standard app. The re-use of CXTPControl and CXTPControls for all control functions in menus, command bars, popups makes creation and manipulation of these much cleaner that the previous code that dealt directly with Windows versions of the same.

It is unfortunate that the documentation proves such a turn off initially that some user can drop the toolkit altogether before discovering its power and beauty. It is well written and easy to find your way around once its "undocumented" architectural concepts are understood.

However, from my communication with XTP they are very aware of the problem and are actively addressing it. Also in their defense I must also add that as I understood the toolkit breadth and depth better I also saw that documenting the complexity of the toolkit will not be an easy task and will take a lot of iterative effort.

Calvi,

Everyone agrees with you, he is just trying to help you out.  This has been discussed at length before.  Be thankful you started with the version you did :)

They are making progress bit by bit.

edit: idiots like me need a lot more hand-holding than average, so Im sure I backed up plenty of their mail folders in the past :)

Blah-blah-blah.

Blah-blah-blah.

Blah-blah-blah.

I have to agree with Andrei, the source code is the best documentation you can get. I didn't use the help file in any way, the source code and the class layout are well designed. I spent some time with the debugger and tried to understand the working model of the Toolkit.

At the beginning (I used another library before) I had some questions how I can achieve some things with the Toolkit and all my support calls (via eMail) are answered.

arc42,

You're the most stupid asshole I've ever met. If only I could get at you I'd beat all sh*t outa you, son of a bitch.