wxWidgets Discussion Forum

Не специалист, но звучит как обычное клиент-серверное приложение. Посмотрите IPC пример и темы, связанные с использованием сокетов.

As for wxCharts...if chosen chart type has support of updating chart data you can update it by timer or whenever it needs. From sample.

Why it should been stored there? If you have event you are already in handlers. And event can have any amount(none, only one or several) of handlers, it just redundant information at all.

Btw, do you know where it's implemented this way?

For escaping '%' you can double it.
Example:

Yeah, thanks, now I see. I am going to open ticket on trac.

According to the documentation wxMoveEvent is holds information about wxTopLevelWindow move change events then why it also generates the event for moving wxButton which isn't wxTopLevelWindow? MCVE: #include <wx/wx.h> #include <wx/dataview.h> class MyFrame : public wxFrame { public: MyFrame(const wx...

Are your sure that VisualStudio use utf8 encoding for file?

Handle OnClose event.

Events in wxWidgets

bandali99 wrote: ↑

Sat Aug 17, 2019 6:59 pm

also, i was looking through custom examples on the wxwidgets tutorial and they made id a type int. What's the difference if its type wxWindow and type int?

It's an alias.
Used for readability.

It would be better if you provided reproducible example. Does this code works for you? #include <wx/wx.h> class MyFrame : public wxFrame { public: MyFrame(const wxString& title) : wxFrame(NULL, wxID_ANY, title) { wxBoxSizer* topSizer = new wxBoxSizer(wxVERTICAL); wxString m_choiceChoices[] = { wxT("...

I don't know why it happens, but usually one can use sizers for widget layouting. So you can do it this way: #include <wx/wx.h> class FrmPrincipal : public wxFrame { public: FrmPrincipal() : wxFrame(NULL, wxID_ANY, "2019") { wxBoxSizer* topSizer = new wxBoxSizer(wxVERTICAL); wxButton* MyButton = new...

How exactly it didn't work? Carets are not restored or they restored on wrong positions?

I've opened a new ticket - https://trac.wxwidgets.org/ticket/18464

It hard to say without full reproducible code but you shouldn't call GUI function from worker thread at all, so it's almost certain the reason of behaviour in that.