wxWidgets Discussion Forum

Maybe the problem is that you're calling ShowModal() inside OnInit(), entering a modal event loop before the application is fully initialized. What if you change to dynamic allocation and non-modal show? class wxDLLApp : public wxApp { bool OnInit() { CExportDlg* dlg = new CExportDlg(NULL); dlg->Cen...

Have you tried topBoxSizer->Layout()? I'm not sure calling RecalcSizes() directly is the correct/sufficient way of forcing layout.

So, to make things short: I hope I fixed this issue. Please do ma favor and test for yourself, just to make sure I didn't do something funny. :) Just one thing. My testing code was not stored correctly, so your final quotes are not much of a testing :P. I edited the original post and voila, everyth...

I was hoping that what I posted was modified on it's way from the database, so that when this is fixed, everything will display properly. Now after clicking edit on my previous post, there was a sad surprise: the code in the edit window is destroyed. With preview before submit, nothing disappears fr...

I would not change any project settings for the library, only add LIBCD (it's the conflicting lib quoted at the bottom of the log) to "Project Properties->Linker->Ignore Specific Library" (or something like that; it's the equivalent of /NODEFAULTLIB linker option). That way the static libr...

There are other overloads for reading numeric values: bool Read(const wxString& key, long* l) const; bool Read(const wxString& key, long* l, long defaultVal) const; long Read(const wxString& key, long defaultVal) const; You can read such value (and you know it's not a string, since you p...

It's a feature. When you click on a slider, the caret moves by "Page" steps towards the click's position. However, I think you can override this behaviour by connecting your own wxEVT_LEFT_DOWN handler. Here 's a similar request and solution. You will have to compute the value for slider.S...

First, the SetWidth/Height methods are IMO a design mistake in wxWidgets -- they don't resize anything (neither reallocate memory nor crop any pixels), just assign some member variables. Don't use them, they're most probably not what you want, anyway. Do I understand correctly that you create a bitm...

The miniframe object is created in the constructor of the main frame. After the miniframe was created a valid pointer to the object exists. When the constructor is left and another method is getting called like the event handler the pointer does not point anymore to the address of the miniframe obj...

I noticed some strange behaviour long before the update -- sometimes text between sharp braces disappeared. The problem was '<' not replaced by < in HTML code, causing trouble to browsers. But back then it only happened outside tags (I think). I devised a workaround, placing either a space or [b][/b...

Here, in App::OnInit(), you pass the wrong handler to thread's ctor: WorkerThread *thread = new WorkerThread(this); ...so the thread sends events to the app object. Probably you wanted to write: WorkerThread *thread = new WorkerThread(frame); The funny thing is if you did it the other way round, tha...

After a little bit of confusion about the coordinates I used the following method to get the exact point on which the mouse was clicked. wxPoint position = ScreenToClient(event.GetPosition()); position.x = (-1)*(position.x) + (2)*(event.GetPosition().x); position.y = (-1)*(position.y) + (2)*(event....

I really don't know how to solve it directly. You can create a custom event and post it to the frame in App::OnInit(). That way you will do it outside the ctor. Look here , just skip the first three paragraphs, replace "Hello world!" with the URL of the page you want to display and use Add...

I think the problem is that when the first match is selected, the insertion point is still at the start of it, so your later search finds the same occurence. Try adjusting the starting point according to current selection: long p1, p2; GetSelection(&p1, &p2); // extract the portion of the te...

pFVertX = (double*) malloc(sizeof(double)); pFVertY = (double*) new double; pFVertZ = new double(); Looks like you've tried different ways of allocation. Apart from the fact that dynamically allocating memory for a single value is unwise (it's only wasting memory, nothing else), you should stick to...