wxWidgets Discussion Forum

Ough! Neither MAC nor chinesse fonts aren't my specialization but from what I am seeing, the problem consists in the weekday name and the "AM" and "PM" strings. That means, in the wxDateTime::GetWeekDayName() and wxDateTime::GetAmPmStrings() on MAC and Chinesse. First of all, ver...

All links from your page to all repository branches are "forbidden" for some reason, David. At least for me.

I need to create a simple table in a class derived from wxRichTextCtrl. I tried to ape the wxRichText example and wrote: wxTextAttrEx tattr; wxArrayInt tabs; wxString tabchr = wxString(static_cast<wxChar>(0x09),1); // another attempt: wxT("\t"); No improvement. tabs.Clear(); tabs.Add(400);...

If you get the "select" event first then your problems are over. Set a flag at "select", process at "deselect". You could get the "select" event first: "select first, then deselect" is the correct way of suppressing flickering of a ribbon bar cursor ...

IMO, the same problem as with "double click". First, you get a "single click" and then a "double click" if it was really a double click. You cannot decide at the "single click" whether it is a double click or not. Similarly, at deselect event you cannot see wh...

wxRichTextCtrl has BeginLineSpacing() - EndLineSpacing() "brackets", wxRichTextAttr has GetLineSpacing() method. The wxRichTextCtrl has also GetDefaultStyleEx() method which can be used for obtaining wxRichTextAttr for subsequently inserted text.

Many problems ahead. For example, text backgound (the user can change this in the system settings), font size (the same), buttons on the titlebar, redrawing (the user has moved something over the titlebar so that the titlebar has been invalidated and scheduled for redrawing) and so on.

AFAIK, no chance. The titlebar style is determined by the operating system settings. Your app can only specify the text for the titlebar. This is not the wxWidgets flaw - you do not have any tools for manipulating the titlebar style even at the "low level" (window handles, messages).

Positioning the title text on the titlebar is controlled by the operating system settings and it cannot be changed on per application basis. The application can only specify the text for the titlebar but it cannot specify whether the text will be centered or edge adjusted or what font will be used f...

If I understand well then the original code was wxWidgets but it was un-wxWidgets-ed by using HWNDs for some reason. The way back is rather complicated because you have bags of numbers (HWNDs) which do belong to some objects but you cannot tell which objects they belong to. You would need to make so...

You cannot do such things. (1) You can get a pointer to a wxWindow only for windows managed by wxWidgets. If the window is created otherwise, you cannot get a wxWindow pointer to it even if the window does have a HWND of some kind. (2) You cannot call a method for an unallocated pointer. The pointer...

It is not clear from the post whether the buttons are connected to ChildFrame::plus() and ChildFrame::minus() correctly. Run the debugger and set breaks in plus() and minus(). Click the buttons. Do you break in the handlers? If so then the buttons are connected correctly. Is the value m_width the cu...

Make sure that the children are really children - that they specify their "parents". When the parent get destroyed, all children get destroyed automatically, too. When you destroy the "main dialog", the whole chain of subordinated dialogs get destroyed as well. No need of individ...

Also, during shutdown the close event cannot be vetoed for sure, if the close comes from the 'x' button or a button calling Close() then it can be vetoed. Check with CanVeto().

Nothing more is needed. No need to specify a base class or something similar. If you have wxFormBuilder at hand, try to create a frame and put a wxRichTextCtrl into it. Check what you get in the XRC file and what code will be generated. wxRichTextCtrl isn't known to XRC so that wxFormBuilder smuggle...