VB6 - IDE: how use unicode?

[joaquim]

using the code Designer, how can i paste a unicode charaters?
(ASCII table, the table charaters)
(yes on Add-In)
using the forms 2.0, i can use the unicode... but on IDE?

[Eduardo-]

The IDE is not Unicode. But you can add Unicode support to Property Pages as long as you use Unicode controls.

[joaquim]

"The IDE is not Unicode."
i know that, but honestly we can do it using Add-ins, but i need more info
"But you can add Unicode support to Property Pages as long as you use Unicode controls. "
the forms 2.0 even the RichTextBox can use it(i have the functions for it)
PS: you did excellent things, i'm doing too(clsImage = DIB's + pointers), console template and many more

[fafalone]

To point out the obvious you could use tB instead and everything is unicode without additional code. Unicode forms and controls, unicode property box, unicode editor, unicode function names... You can make your function names using color emojis if you're a psycho.

[joaquim]

what i want is only show all ASCII characters(more the table charaters) on IDE

[Eduardo-]

the forms 2.0 even the RichTextBox can use it(i have the functions for it)

I would use Krool's Common Controls replacement instead.

[joaquim]

changing the font to Terminal is good? but not compatible?

[Eduardo-]

changing the font to Terminal is good? but not compatible?

Only changing the font does not make the IDE Unicode capable.
If Terminal is a good font? Yes, I guess. I use Consolas.
In current Windows all fonts are Unicode ready (unless you install a custom font that is not).

What these fonts are, is that they are mono-spaced (every character occupies the same width). That doesn't have to do with being Unicode or not.

[-Franky-]

The Forms 2.0 controls are not intended for use with VB6 and often lead to unexpected errors or crashes. You should either use other Unicode-enabled controls, such as those from Kroll, or create your own Unicode-enabled controls using CreateWindowEx.

[Elroy]

The biggest problem I ran into trying to make the IDE fully unicode compatible was that it's not supported in the FRM (and other UI) files. Actually, it's not supported for string literals in BAS files either. Without those things, even if we re-write custom property windows, we're just never really going to get there. And, the code windows will never be Unicode either. Maybe that's the biggest problem, as we could rewrite all the controls to save Unicode properties in the FRX (and ..X) associated files. So, maybe it's the BAS files and code editor window that are the biggest hard-road-blocks.