"<Grid VerticalAlignment = 'Center'><TextBlock>%s:  [%s] - [%s]</TextBlock><TextBlock TextAlignment='Center' Padding='50,0,0,0'>%s</TextBlock><TextBlock TextAlignment='Right' Padding='0,0,5,0'>%s</TextBlock></Grid>"

Hi guys,

I am faced with an issue for which I also have an open case with CodeJock. Still I want to hear if anyone else has experience in this matter and hopefully a solution.

We use the report control to generate lists of documents in a collection. Some properties of the documents are shown as markup on the same cell throughout the report control.

The problem that we are facing is that drawing the markup is very slow. We add a little over 3000 records. Most of these records contain markup in a specific column.

The way that we add the markup is more or less identical to your examples. We call EnableMarkup() on the report control and use SetCaption() on the markup item for each record/row.

The markup looks somewhat like this:

The (all in-memory) loading process (before the call to Populate()) on a fast newer pc takes over 13 seconds. If we remove the call to SetCaption(), but still generate the markup, the call is completed in less than 1 second. Is the any way to speed this up (significantly).

Process memory grows from 17 MB to a staggering 240 MB (and 67 MB without markup). There can of course be many reasons for this, but generally all objects are created on the heap. This also means that the application takes a long time to clean up memory afterwards. Especially while using markup it is noticeably slower. Can the toolkit even handle working off the heap or is this required by design.

I tried to rule out errors by simple testing my markup in the Report Sample project and the same behavior is experienced. To stress test it I added loops to define 3000+ records and also apply 3000+ markup calls. When I use the default sample markup in cstrMarkupShortSample, it loads reasonably fast, but once I use our own markup it slows down noticeably.

I tried some even simpler markup on all 3000 records:

This loads fairly fast, but the process memory is still quite high and it takes a long time to destruct all objects in the memory upon exiting the running application. 

This really makes me wonder if markup is even recommended in report control, when it is used broadly and for many records? 

Or is the purpose of the markup in the report control only to support very simple stuff, such as changing the color or boldness of a single word?  

A few details about my setup:

Product: Toolkit Pro for Visual C++ MFC

Product version: 18.4.0

Development platform: Visual Studio 2017 (toolkit v141)

Language(s): C++ 11, 14, 17, MFC

Operating system: Windows 10 Enterprise (64 bit) 1803

Relevant project settings: 32 bit, Unicode, MFC in shared DLL, _XTP_STATICLINK

Windows SDK: 8.1

Processor: Intel Core i7-6770HQ @ 2.60GHz

Memory: 16GB

Storage: 2 x 250 GB NVMe (not configured as raid)