wxWidgets Discussion Forum

wxSpinCtrl

One of the parameters of the constructor is style. wxTE_MULTILINE is one of the possible styles.

First of all, are you using wxTextCtrl or something else?
For the wx component, did you create it as a multi-line control? It has AppendText(), and operator<<(), so you should really be fine with it.

Notice that wxRichTextCtrl support in XRC is available in wxWidgets 2.9.5 and later only and you need to explicitly register its handler using

Code: Select all

#include <wx/xrc/xh_richtext.h>
AddHandler(new wxRichTextCtrl);

to use it.

https://docs.wxwidgets.org/trunk/overvi ... chtextctrl

Hi Kiba, [You probably won't find many users around here that will answer you in French] You are allowed to create your closed source app with private license, or commercial license, or any other kind, and there is nothing to pay for using wxWidgets. You don't set a type of license in wxAboutDialogI...

Create the wxTextCtrl with wxTE_NOHIDESEL flag.

Run your app outside VS and it should tell you which dll-s it cannot find.

GetValue() returns a wxString, which is not [necessarily] a std::string, so some mechanism might be needed for conversion, and using mb_str() is one of them. mb_str() returns wxCharBuffer, which is convertible to char*. If conversion works for you without the call to mb_str(), you might be using wxW...

let's assume I'm confusing the "Unicode" with "utf-16" / "UCS-2". What does this have to do with the title of my post? It was very misleading, including the mix-up with utf-8 representation. How do I escape characters like 0x0500 and 0x0c00 (and some others I have here)? You surely meant 0x000c, bu...

FWIW it does look like a bug. The same happens with the latest git sources too.

you can see that the UTF-8 ENQ is 0x05 (the same as ASCII) and the Unicode is 0x0500. ..this time I think it's perfectly clear -- you are confusing "Unicode" with "utf-16" / "UCS-2". "Unicode" is not an encoding, while utf-8, utf-16, ucs-2 are all encodings intended to represent Unicode. Again, 0x0...

The UTF-8 representation of 0x0500 (unicode) is the same as UTF-8 (0x05) Uhm, no, it is not. Unicode U+0500 can be represented in utf-8 as 0xD4 0x80 (and FWIW as 0x0500 in utf-16). but with only one char. There is no such thing. You are probably confusing a misinterpretation of utf-16 0x0500 value ...

There is wxFont::AddPrivateFont().

lupusc wrote: ↑

Sat Aug 08, 2020 3:42 pm

"../configure --with-gtk" fails, telling me that neither GTK+-3.0 nor GTK+-2.0 nor GTK+-1.2.3 is present. This is strange because the system is working properly with the GNOME Desktop (UBUNTU 20.04)

You need the development packages for the GTK version of your choice (i.e. libgtk-3-dev).

Did you mean "non-printable" as in "not on the keyboard"? Because it looks like 0x0500 does have a glyph. And you probably need to escape it inside the wxString that you use to write the xml, in which case you'd be better off by finding its utf8 representation and using that, which in your case shou...