|
-
Oct 22nd, 2014, 10:59 AM
#10
Re: CommonControls (Replacement of the MS common controls)
Say Krool,
FANTASTIC work. I love the idea of having absolutely no OCX dependencies, without losing programming features.
I saw a comment above though about Unicode on the standard button. Actually, this is no biggie at all. I've attached a small project that does it. The BAS module even has several other calls for doing Unicode things.
Also, it's not in there, but it's quite easy to write a CTL control based on little more than the button that saves Unicode from the IDE. There are two tricks to getting this done: 1) You have to save the .Caption property into a byte array in the PropertyBag so that it's coerced into the .FRX file when you do a save. The .FRM files are strictly ASCII so you can't save Unicode properties in them. The second trick is that the actual Property Window won't handle Unicode either, so you have to design a custom property window for the button .Caption property using the RTF control with its Unicode turned on.
However, neither of those is terribly difficult.
Take Care,
Elroy
UnicodeButton.zip
Edit: Ahhh, and I've actually done this but not cleaned it up for distribution. In my opinion, if you're going to write a custom user control for a Unicode button, it should have the RTF box (for the Unicode property) actually on the control itself (in other words, no extra forms as support for the control). Maybe you'll be motivated to do this with your API version of the RTF box. Again, great work though.
Last edited by Elroy; Oct 22nd, 2014 at 11:07 AM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|