Gotcha, as long as it’s still easy to use so that somebody who has custom loaded their font families can register them with the library. Keep in mind these could be either file or memory fonts, right now the control works with either, which is great and would be nice to keep it that way.
Are you planning on keeping the custom font submission global, or per control? Global met my needs and was simple, but there could in theory be somebody who wants to use one set of fonts for one control, and a different set for different control…but I didn’t need that as I only have one instance of HtmlPanel.
Also, as mentioned in the other thread I have selection text fore and back color working, Right now they are both simply constants that you can hardcode in CssUtils (selection backcolor was already there, but I added forecolor). As part of adding this I made the selection be whole-word just like in Outlook / Word / IE. Anyway, it would be fantastic if the ::selection style was honored. I didn’t bite that off because hardcoding it into the code of my custom build was acceptable for now. But it would be great if ::selection style was honored.
Later,
Ryan
Are you planning on keeping the custom font submission global, or per control? Global met my needs and was simple, but there could in theory be somebody who wants to use one set of fonts for one control, and a different set for different control…but I didn’t need that as I only have one instance of HtmlPanel.
Also, as mentioned in the other thread I have selection text fore and back color working, Right now they are both simply constants that you can hardcode in CssUtils (selection backcolor was already there, but I added forecolor). As part of adding this I made the selection be whole-word just like in Outlook / Word / IE. Anyway, it would be fantastic if the ::selection style was honored. I didn’t bite that off because hardcoding it into the code of my custom build was acceptable for now. But it would be great if ::selection style was honored.
Later,
Ryan