[quote=187882:@Jon Ogden]I understand what you are saying completely. However, if they can get images to display in an image view control, it should be able to be done in a canvas.
I just took your project and made a control group of the canvases and created about 36 of them. It took about 13 seconds for the images to all load. Nothing loaded until after 10 seconds. Now, I’m surprised they actually did load. I get cases where some images never load. But then again, there’s more code running in my app and more stuff going on.
I don’t think it should take 13 seconds to load a picture that is 148 kB in size into 60 pixel x 60 pixel canvases. Something is just not right there. And that is ONE picture. If you have different pictures for each canvase it gets even worse…
Yes, canvases are great at drawing lines. But these days showing graphical content and pictures is what it is all about.
And yes, in my case I was able to use an image view. Fortunately, I’m not having to do anything other than show the picture really. On the desktop, I do a little more with this part of the app and so having the capabilities of the canvas is important.
And then to not even have a control set visible in the properties of the web page - I don’t understand that. I know control sets in web are quite a bit different but unless you have an array property of the defined type in your window, you have no way of viewing the properties of the items in the control set.[/quote]
Just like in Desktop, WE uses native controls. From what I can tell by the pages DOM code, it uses HTMLCanvas. https://en.wikipedia.org/wiki/Canvas_element
Talking about fast, nothing is probably faster than the good old IMG HTML Tag
<img style="width: 233px; height: 200px;" alt=""
Better yet, it resizes automatically the picture to make it fit, unlike ImageView. That is probably by far the fastest way of displaying images. It should not be very difficult to use a Web Control Wrapper to create your own custom control based on it.
I do understand your frustration. It seems a part of what is happening to you can be avoided by going straight to the HTML Control instead of letting Xojo impose an additional layer of complexity.