11-15-2022, 05:04 PM
CHR$(240) is a mapped unicode character, so it's going to display, by default, whatever code page your OS is configured for. (In this case, you're getting the o with the accent over it.)
As far as I can guess, the only way you'd work around this is to use wide characters and call the windows call to set the title yourself.
https://learn.microsoft.com/en-us/window...indowtextw <-- use this for the windows API call to the unicode characters.
^ And I'm thinking the above should give you the actual unicode characters that you'd bee looking for.
I'm lazy (and running back and forth to the kitchen cooking breakfst), so I haven't tested putting the pieces together yet, but it seems as if they should do what you want.
As far as I can guess, the only way you'd work around this is to use wide characters and call the windows call to set the title yourself.
https://learn.microsoft.com/en-us/window...indowtextw <-- use this for the windows API call to the unicode characters.
Code: (Select All)
_TITLE CHR$(240) + "Foo"
i% = _MAPUNICODE(240)
t$ = MKI$(i%)
title$ = t$ + "F o o "^ And I'm thinking the above should give you the actual unicode characters that you'd bee looking for.
I'm lazy (and running back and forth to the kitchen cooking breakfst), so I haven't tested putting the pieces together yet, but it seems as if they should do what you want.