Hello!
Please add back support of v 1.0 src="property:" and src="method:" image sources. There are certain instances when it is very convenient to use this approach:
- Handling events manually is extra overhead
- Supplying the base-64 value inline is also an overhead if you have to do it in many different places
- Loading from file/web for small icons is not convenient either
- Most icons/images are stored as resources and used as such in other controls. So, when you use property: to refer to such an image resource, it's very easy to do and you don;t have to change anything or write new code.
- Sometimes, although certainly an exotic use case, you may actually rely on a property/method to provide a dynamic image every time.
In our case, I had to manually add back this functionality by adding old code back to ImageHandler. It was trivial, so I think it would not hurt if such support would remain.
We use HTML Renderer in our custom tooltip control. And because we had hundreds of tooltip texts "baked-in" and scattered all over the place, changing them all would be very time consuming, so we had to add back support for the old image source format manually.
Comments: Thank you for a quick response and a suggested work-around! Yes, we have several major apps that have hundreds of html text strings either hard-coded or dynamically generated that rely on those image sources. In any case, unfortunately your suggested work-around will not work for us, as we do not use the built-in HtmlToolTip and use our own custom ToolTip control instead. This custom control simply uses HTML rendering features of the library, now using HTMLRenderer static class. Unfortunately this class provides no events to subscribe to. We tried using HTMLContainer at first, but for some strange reason it resulted in image sizes being calculated incorrectly, so we had to adopt static HTMLRenderer.
Please add back support of v 1.0 src="property:" and src="method:" image sources. There are certain instances when it is very convenient to use this approach:
- Handling events manually is extra overhead
- Supplying the base-64 value inline is also an overhead if you have to do it in many different places
- Loading from file/web for small icons is not convenient either
- Most icons/images are stored as resources and used as such in other controls. So, when you use property: to refer to such an image resource, it's very easy to do and you don;t have to change anything or write new code.
- Sometimes, although certainly an exotic use case, you may actually rely on a property/method to provide a dynamic image every time.
In our case, I had to manually add back this functionality by adding old code back to ImageHandler. It was trivial, so I think it would not hurt if such support would remain.
We use HTML Renderer in our custom tooltip control. And because we had hundreds of tooltip texts "baked-in" and scattered all over the place, changing them all would be very time consuming, so we had to add back support for the old image source format manually.
Comments: Thank you for a quick response and a suggested work-around! Yes, we have several major apps that have hundreds of html text strings either hard-coded or dynamically generated that rely on those image sources. In any case, unfortunately your suggested work-around will not work for us, as we do not use the built-in HtmlToolTip and use our own custom ToolTip control instead. This custom control simply uses HTML rendering features of the library, now using HTMLRenderer static class. Unfortunately this class provides no events to subscribe to. We tried using HTMLContainer at first, but for some strange reason it resulted in image sizes being calculated incorrectly, so we had to adopt static HTMLRenderer.