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?
Printable View
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?
The IDE is not Unicode. But you can add Unicode support to Property Pages as long as you use Unicode controls.
"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 ;)
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.
what i want is only show all ASCII characters(more the table charaters) on IDE ;)
I would use Krool's Common Controls replacement instead.Quote:
Originally Posted by joaquim
changing the font to Terminal is good? but not compatible?
Only changing the font does not make the IDE Unicode capable.Quote:
Originally Posted by joaquim
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.
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.
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.
yes i miss understood:
0 - unicode is the charaters code!!!
1 - font is the grafic\print way;
even, if i'm wrong, please correct me(i'm learning now :P )
The biggest problem lies in how the vb6 compiler uses unicode.Quote:
Originally Posted by joaquim
using Add-ins:
1 - can i detect when IDE saves the files(thinking on event)?
2 - can i save the file using the unicode codification?
This is for compiling files encoded in utf8 (without going through an IDE, directly using the command line for compilation)
Any unicode character will fail to compile. Currently, the only way to obtain unicode is Twinbasic
Attachment 196199
i'm sorry, but i can't se the image: "Invalid Attachment specified. If you followed a valid link, please notify the administrator"Quote:
Originally Posted by woeoio
ok.. i can't use unicode on IDE, but we can use it with forms 2.0 and RichTextBox ;)
my big objective is better ;)
using Terminal font name, i can draw all ASCII charateres on a listbox without problem...
the IDE is Terminal too(i changed), for paste it... but if i draw\write 'á'(like my keyboard have a different layout), i will get beta charater :(
so what is is the best font name for resolve it?
(if i need download one, i can do it ;) )
It doesn't matter. The attachment is just a screenshot of an error when I compiled a vb6 file encoded in unicode using the command line.Quote:
Originally Posted by joaquim
It is indeed possible to solve the display issue by using Unicode-supported controls. Moreover, if unicode characters are used in the ide, they can also be converted to unicode encodings like \u4F6H.
But I don't understand what you mean by changing "ide" to "terminal". Could you provide a screenshot for me to enjoy
ok... i'm sorry, my English can be confused.. i'm sorry..
my VB6 IDE Font name, now, it's Terminal!!! because it can draw all ASCII characters!!!
but isn't compatible with keyboard layout(like 'á'(combination keys) = beta.. tested)
This behavior is actually very typical, and it’s not a bug in VB6 itself — it’s a limitation of the Terminal font.
Why this happens
Terminal is a DOS/OEM bitmap font.
It was designed to cover ASCII and OEM character sets only, not Unicode.
Because it is not a TrueType font, it has no support for combining diacritics or modern keyboard layouts.
That’s why:
• All ASCII characters render correctly ?
• Dead keys and composed characters fail ?
Your example is spot on:
Key combination Expected Terminal result
' + a á ? or wrong symbol
~ + n ñ incorrect mapping
This happens because Terminal simply does not contain combining character tables.
How VB6 handles fonts
The VB6 IDE:
• Is ANSI-based internally
• Relies heavily on the selected font for input parsing
• Does not fully support Unicode-era input methods
So choosing Terminal effectively forces the editor into DOS-like behavior.
Recommended solutions (from best to worst)
? Option 1: Use a TrueType monospace font (recommended)
If you want:
• Monospaced rendering
• Clean ASCII display
• Proper keyboard layout support
Try these:
• Consolas (modern, clear, Windows default)
• Lucida Console (closest visual match to Terminal)
• Courier New (maximum compatibility)
• DejaVu Sans Mono (excellent character coverage)
• Fira Code / Cascadia Code (modern aesthetics)
? Lucida Console is usually the best compromise.
? Option 2: Limit Terminal to output only
Use Terminal only for:
• Debug logs
• Fixed-width text alignment
Keep a Unicode-compatible font for editing.
?? Option 3: Keep using Terminal (not recommended)
You can, but you will lose:
• Composed characters
• International keyboard support
• Any non-ASCII input reliability
Only reasonable if you are building something explicitly DOS-style.
Summary
Terminal is a display font, not an input-compatible font.
It can draw ASCII perfectly, but it cannot handle modern keyboard input.
In VB6, choosing Terminal trades input capability for rendering fidelity.
The above is the answer I have analyzed your question through ai
Perhaps this vbccr control is also a good choice, as it is more abundant than form2.0.
VBCCR Development Manual | VB6 PRO DOCS
https://doc.vb6.pro/en/packages/vbccr/
to be honest, i must use the Terminal for show all ASCII characteres.... if you know the Terminal 2.0 or similar(with keys combination), please tell me
ok..
1 - Terminal is good for draw charaters, but not keyboard input;
2 - for use unicode, what is the best font?(for show any characteres)
Terminal shows a nonstandard set of characters so it's not just a question of supported codes.
For example
Attachment 196336 in Terminal will look like ·¶ÎÈ in any other font even though they're the same character codes.