Although it seems that to transfer the appropriate data to the device context is the 'right' solution, I have a hunch that it will be a difficult task. So I am beginning to think that we should take another, a cheat, approach.
It's like a chroma key. Uniscribe draws text with a color background instead of transparency, and a word replaces the color with transparency when converting from the bitmap to an Factor's image. It may be slow, but we don't have many chances to draw characters on a transparent background. And for example, on a button label, once Factor creates an image with such characters, Factor use the image again, so I think there are few problems. This approach can localize changes. I can't define the word for image conversion to do such a special action, but I think that it's not a difficult task for someone familiar with image processing words. > 2019/05/30 1:59、Alexander Ilin <ajs...@yandex.ru> のメール： > > Wow, you are making a very valuable contribution! > Thank you very much for the effort you are making! > > It would be really great to have a solution for this issue. > > 29.05.2019, 05:39, "KUSUMOTO Norio" <kusum...@na.rim.or.jp>: >> It seems that the direction to solve the problem is not wrong. >> But, we will need to transfer the appropriate data with the appropriate >> offset to the device context >> where Uniscribe writes a text. >> >> <https://pbs.twimg.com/media/D7s4qrTXYAIk8WF.png> -- KUSUMOTO Norio _______________________________________________ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
