wxWidgets Discussion Forum

Your code is too long for a starter. I recomend to study the samples/minimal provided with wx installation. Then see other samples and learn how to add features (file dialogs, drawing, etc). Right now, your code lacks a class (say "MyApp") deriving from wxApp , and which overrides wxApp::OnInit() . ...

I compled the opengl sample again and it works perfectly. I probably expected one .exe, and there is three as you know. What? There are four OGL samples. You can compile one by one (entering in each sub-dir) or all at once from samples\opengl I ran the drawing-sample. That the one that throws the "...

I don't see you call event.Skip() at Beast_1_69Dialog::OnClose(...), supposed Beast_1_69Dialog derives from wxDialog.

Let wx does its job instead of closing/destroying the window on your own.

wxmsw$(wxShortVersionString)u_core.lib wxbase$(wxShortVersionString)u.lib I suppose (wxShortVersionString) is some define for "3.1" Also, if you use wxSocket, then add wxbase31ud_net.lib (or similar name) For the system libs, I use the same libs as you, plus these three: odbc32.lib opengl32.lib ole...

Between wx3.1.0 (Feb 2016) and wx3.1.1 (Feb 2018) there has been some change in the libs needed for Windows target. At least oleacc is required now.

You may take a look at minimal sample project to find out the requiered libraries.

You can create your own cell editor, deriving from a wx's one. You must override some virtual methods: class myGridCellChoiceEditor : public wxGridCellChoiceEditor { public: ...... virtual void Create(wxWindow* parent, wxWindowID id, wxEvtHandler* evtHandler); virtual wxGridCellEditor *Clone() const...

wxSmith is a plugging of Code::Blocks. If you have built C::B on your own then you missed to build also pluggins. To use wxWidgets no wizard is needed. You can always add the required libraries and headers on your own. It happens that on Linux wx has a useful tool called "wx-config", which can do th...

Take a look at my post FAQ: wxWidgets and OpenGL
viewtopic.php?f=27&t=45552

People often gets confused with OpenGL. They think it's like any other system library. And worst, they think the IDE they use provide OpenGL as any other common functions. I understand that without a previous knowledge such misunderstandings are there. Here are some tips. Q. What are "display attrib...

By the time IsBeingDeleted() is called, you can't be sure that the frame still exists, so that pointer can point to an invalid instance.

There are two points where you must NULL that pointer: a) Right after memoryeditor->Close() b) In your MemoryEditor ctor pass a pointer to the main frame. Have a "make memoryeditor NULL" method in the main frame. When the MemoryEditor closes (handle this event), call that method in the main frame: m...

If you close that other frame and don't set memoryeditor = NULL (which is done with wxDELETE(memoryeditor)) then the next time you click the button the memoryeditor->IsIconized() branch is executed with an invalid pointer.

I guess you don't update "memoryeditor" pointer after memoryeditor->Close()
Can't know, not enough code.

If you use wxWidgets then you don't need GLFW, as they will fight for window and context handling. GLEW is a lib for retrieving function pointers to gl-commands. You can use precompiled files, or you can add them (2 or 3 files) to your app and compile them normally. Which are your problems, so far?....

PB wrote: Is it not?

Dam. PB, you're right.
I found the commit... May 31, 2009
Actually, it was added to wx 3.0. Not to wx 2.9