wxWidgets Discussion Forum

I'll solve my own here -- The key is that macosx-version-min isn't working fully here. You'll need to force the use of the 10.6 SDK as well. ./configure --with-cocoa --disable-shared --with-macosx-version-min=10.5 --enable-macosx_arch=i386 --with-macosx-sdk=/Applications/Xcode.app/Contents/Developer...

Running 2.9.4 SVN, I compiled wxWidgets up on Lion with: ../configure --with-cocoa --disable-shared --with-macosx-version-min=10.5 --enable-macosx_arch=i386 That should give me a nice 10.5-able library. It'll use the 10.7 SDK but ensure calls are fine even down to 10.5. They're not, it seems. Even t...

Thanks! Big Doh-slap on that one... For posterity, here's the simplified code: class ScriptDataViewListModel: public wxDataViewListStore { public: virtual bool GetAttrByRow( unsigned int row, unsigned int col, wxDataViewItemAttr &attr ) const; }; bool ScriptDataViewListModel::GetAttrByRow( unsigned ...

I'd like to have a wxDataViewListCtrl that will draw several cells differently than others. So, I've derived my own version and have an override of GetAttrByRow: class ScriptDataViewListCtrl: public wxDataViewListCtrl { public: ScriptDataViewListCtrl(wxWindow* parent, wxWindowID id) : wxDataViewList...

Thanks - I'd checked that and that wasn't the issue. Reads, writes, etc. were actually going through. After going back to an earlier version and adding in about a month worth of patches, I finally tracked down the issue. A library I was using had a header file that specified: #pragma pack(1) Why the...

Pulling my hair out on this one. Consider the following code: bool MyApp::OnInit(void) { wxTextFile *foo1 = new wxTextFile(_T("foo1.txt")); if (foo1->Exists()) foo1->Open(); else foo1->Create(); foo1->AddLine(_T("arg")); foo1->Write(); foo1->Close(); delete foo1; I've used wxTextFile a good bit and ...

Thanks Jorgen,

I've got things going right now with that mutex'ed counter. Since I know both threads should take about the same amount of time, it's not too horrific, but just doing some wxMilliSleep calls in a loop until that changes is a kludge it seems.

Craig

I'm fairly new to multi-threading, so I'm looking for a little help on how to set something up properly. I've got a function that forks off two worker threads to crunch a bunch of numbers. In the past, I've been able to just have each thread work on half the data and have the main function wait unti...

I have a modal dialog that lets users drag things around. I trap the release events just fine and do what is supposed to happen on release. The problem is that as folks are dragging around, the mouse can leave the window, of course. If they come back with the mouse button still down, all is fine. Bu...

Jim,

Yes, I've posted events like this before, but what's the best way to wait as non-invasively as possible? Just having a loop with a sleep and a yield in there slows things down a good bit.

Craig

I currently run several dialogs as modal dialogs. They let users adjust parameters the results of which are shown on screen. I'd like to have these be modeless dialogs so that several aspects of the display can be changed in separate areas of the GUI, though. Main program execution needs to wait for...

I've got an app that has a good reason to use command-M for something other than Apple's default of minimize for the shortcut. Just putting it in an accelerator table though doesn't trap it. Can we override the OS defaults for keys?

Craig

What I do is similar to the RegisterHotKeys, but I've got an accelerator table already setup for shortcuts. Inside my frame's constructor I do: wxAcceleratorEntry entries[14]; entries[0].Set(wxACCEL_CTRL, (int) 'O', MENU_LOAD_FILE); ... entries[12].Set(wxACCEL_NORMAL, WXK_SPACE, KEY_SPACE); entries[...

OK, I figured it out. Credit goes largely to this thread here: http://forums.wxwidgets.org/viewtopic.php?t=13304 In there was the comment that you can't write to the server directly. What took me a bit to grok was that the solution is actually quite simple. When the connection is made, we fire of On...

I have gotten basic wxSocketServer / wxSocketClient functionality going using the samples. Connections are made, the client can send data to the server, the server gets the data, and the server can even return information to the tune of "OK, yes I got your command". So far, so good. Writing this way...