Thank you for looking into this issue, please find enclosed sample projects for 15.2 and 13.1. We are able to see the difference between the two versions. In our application, it's worse.

Thanks,

Crystal.

Hi Mike,

While I was migrating our production code over to the sample application, I came upon the code where we build the HTML for the FormattedTextEditor. We keep our images as embedded resources in the project and use the following syntax for embedding the image in the cell:

var encodedImg = FormattedLinkEditor.EncodeImage(Properties.Resources.ImageX);
var html = $"<img data="{encodedImg}" />";
ultraDataRow["Column1"] = html;

I recalled that there is an alternate way of adding images to the cell by using the src tag, with a file path to the image, and tested the following in the production code:

var html = @"<img src=""C:\Test\Imagex.png""/>";;
ultraDataRow["Column1"] = html;

The performance issue immediately went away using the src tag. It seemed to even be more performant than the "fixed" 2118 SR version using the data tag. It looks like the issue is in rendering the image using the data tag. The images being loaded are all 16x16 32 bit png around 660 bytes, nothing huge.

I have implemented a work around for the performance issue in the production code by using the src tag and putting all the images in a folder on disk instead of embedding them as a resource. While this isn't a perfect solution, I believe it will work as a patch to our code for our customers as this will have minimal impact on regression testing.

Is there any way of loading the images from embedded resources and using them with the src tag instead of loading them from disk? This would remove the dependency of having the images deployed to disk and read from there. Do you see anything out of the ordinary with how we're using the data tag with an encoded embedded resource?

If you have any other suggestions, that would be greatly appreciated.

Thanks,

Lindos.

Hi Lindos, 

Just to be sure I understand, in the code you posted here, ImageX is a string that contains the encoded version of the image for the XML? So that means that the performance issue is occuring when the FormattedTextEditor is parsing the encoded image. Hm, I can't imagine how THAT would have changed. My guess is that it didn't, and it just always been more efficient to use a file instead of a string. But it's great that you found it.

To answer your question - no, you can't use an src tag and point to an embedded resource. Although I guess in theory, you could store the image in your application as an embedded resource, then load that image into memory and then save it to a file, rather than distributing it separately with the application. You could dump it into the same folder as the exe or maybe into the machines Temp folder. Not ideal, but probably not terrible, depending on the size of your images.

We're coming up on the release for 19.2, so I'm a bit swamped at the moment. If you can send me a sample, I'd still love to check it out. But if I can find some time, I will try to do a little testing myself using images with a data tag. 

Hi Mike,

Clarifying what ImageX is.

In the Visual Studio project, a Resource file (Resources.resx) is added to the project under the Properties folder. Opening up the Resource file in Visual Studio you can select the Images section from the dropdown. The Images are added to this section by drag and drop from Windows Explorer where the image filename becomes the key in the Resource file. The Resource file has a build action of Embedded Resource.

The embedded images are referenced from the Resource file in code using the following:

var image = Properties.Resources.ImageX;

Where ImageX is the name of the image in the resource file.

We did discuss keeping the images as is, embedded in a resource file, and writing them to disk at the time they were needed. This option was ultimately rejected due to business needs and the decision to deploy the images up front in a folder was made.

If I can reproduce the issue in a sample project I will definitely send it your way.

Thanks for your help.

Lindos.

Okay, that makes sense. Not sure why I was confused - it seems perfectly obvious from the code, now. 

In what event are you setting the value of the field in the DataRow. I assume that's done before you bind to the grid. Or are you dynamically building or changing the data as you scroll, like in the InitializeRow event of the grid or something?

The value of the field in the DataRow is being set when we update the UltraDataSource for the grid. This happens as we navigate from one business object to the next (the grid data is refreshed for each business object by first clearing the rows collection in the UltraDataSource). The code spins through a collection (the row data) in the business object and calls the UltraDataSource objects Rows.Add() method for each new row. Each new DataRow's column values are then updated. After all the data has been loaded we don't update it any further. From this point on (until the next business object is loaded) the data remains static.