Hi baert,
isn't that what wxEvent is meant for?
There's an example in samples\event in your wx folder, you may want to have a look at that.
HTH, Chris
Search found 150 matches
- Thu Feb 09, 2006 6:24 pm
- Forum: C++ Development
- Topic: work with a queue
- Replies: 3
- Views: 1056
- Thu Feb 09, 2006 6:13 pm
- Forum: wxDev-C++
- Topic: Supporting alternative libraries debug/unicode etc
- Replies: 10
- Views: 1881
I was thinking of something besides the compiler options. I meant an additional switch solely for providing the wx specific stuff. If you've got special options (like defines) for both the compiler and project options, you'd have to add those to each profile you create (wx ANSI/Unicode, Debug/Releas...
- Thu Feb 09, 2006 11:13 am
- Forum: wxDev-C++
- Topic: Supporting alternative libraries debug/unicode etc
- Replies: 10
- Views: 1881
I'd really like that. This could simply be done by letting the user select a profile that sets the relevant compiler options. Those profiles could be wx-ANSI-Debug wx-ANSI-Release wx-Unicode-Debug wx-Unicode-Release. The selected profile would have to be stored in the project file. Also selecting a ...
- Wed Feb 08, 2006 9:56 pm
- Forum: wxDev-C++
- Topic: Supporting alternative libraries debug/unicode etc
- Replies: 10
- Views: 1881
- Wed Feb 08, 2006 2:55 pm
- Forum: wxDev-C++
- Topic: Supporting alternative libraries debug/unicode etc
- Replies: 10
- Views: 1881
- Sun Feb 05, 2006 6:06 pm
- Forum: wxDev-C++
- Topic: Regarding devpak for 6.9beta
- Replies: 3
- Views: 1102
Hi NinjaNL, unfortunately I'm getting syntax errors when trying to use the makefile (configure&&make works fine): mingw32-make -f makefile.gcc BUILD=release MONOLITHIC=1 USE_OPENGL=1 USE_XRC=1 USE_ODBC=1 RUNTIME_LIBS=static USE _RTTI=0 USE_EXCEPTIONS=1 if not exist gcc_msw mkdir gcc_msw /usr/bin/sh:...
- Sun Feb 05, 2006 3:30 pm
- Forum: C++ Development
- Topic: wxString::Format uint64_t problem
- Replies: 23
- Views: 6143
Hi Bahman, Ooops, there shouldn't be qoutes around it of course: cout << wxLongLongFmtSpec << endl; :oops: And yes, I added "%I64" to wxVsnprintf_. I also noticed that "%ll" isn't properly supported, too, should may be I should add that, too. I asked in the wxDevCpp subforum for a debug build of a d...
- Sun Feb 05, 2006 1:08 pm
- Forum: wxDev-C++
- Topic: Regarding devpak for 6.9beta
- Replies: 3
- Views: 1102
Regarding devpak for 6.9beta
Hi, As seen in this thread some devpaks have problems with wxString::Format and friends when using 64 bit integers. I'd like to debug this some more and would like to ask the creator of the devpak for 6.9beta (which shows this behaviour) for two things: 1. The exact command used to build wx. 2. If p...
- Sun Feb 05, 2006 12:44 pm
- Forum: C++ Development
- Topic: wxString::Format uint64_t problem
- Replies: 23
- Views: 6143
Hi, I couldn't find out why the host's vsnprintf isn't called. I suspected if to have to do something with using the Makefile.gcc instead of the one generated by configure and then running into some wierd #ifdef troubles, but there are far too many preprocessor directives used for me to understand w...
- Sun Feb 05, 2006 11:48 am
- Forum: Compiler / Linking / IDE Related
- Topic: gcc segmentation fault while compiling
- Replies: 1
- Views: 929
Hi feua, internal compiler errors are a bug the compiler (cygwin), so technically it's not a wx problem. If possible you should try to update the compiler to a newer version. However, if this is not possible: The ICE seems to occur with precompiling the headers. You should be able to turn off those ...
- Sat Feb 04, 2006 5:07 pm
- Forum: C++ Development
- Topic: wxString::Format uint64_t problem
- Replies: 23
- Views: 6143
Hi Bahman, just wanted to report back with my findings so far: The crashes are indeed caused by a bad pointer coming from va_args in wxVsnprintf_. I was able to patch this function to support %I64 modifiers. This would make the problems go away, but there is still the outstanding question why wxVsnp...
- Fri Feb 03, 2006 4:34 pm
- Forum: C++ Development
- Topic: wxString::Format uint64_t problem
- Replies: 23
- Views: 6143
Hi Bahman, Such irritating program behaviour always gets me interested :wink: I don't have time today to look into this more, so I'll continue tomorrow. Short roundup of my investigations: - In wxDevCpp's devpak wx's internal vsnprintf substitute (wxVsnprintf_) seems to be called. That one doesn't k...
- Fri Feb 03, 2006 11:24 am
- Forum: C++ Development
- Topic: wxString::Format uint64_t problem
- Replies: 23
- Views: 6143
Hi, cout << wxString::Format( "%" wxLongLongFmtSpec "u %s", wxULL(2), "hello world\n" ); crashed for me in wxVsnprintf_ when using the wxMSW 2.6.2 devpak from wxDev-Cpp 6.9beta (MinGW 3.4.2). To get a useful backtrace I compiled wxMSW 2.6.2 myself, with "configure --disable-shared --enable-debug". N...
- Thu Feb 02, 2006 7:04 pm
- Forum: C++ Development
- Topic: wxString::Format uint64_t problem
- Replies: 23
- Views: 6143
(The joke is I ran across -I64 yesterday, misread it as -OneSixtyFour and therefore got no result :) Ah, the good old "Il1"-problem :wink: cout << wxString::Format( "%I64u %s", (uint64_t)2, "hello world\n" ); crashes the program, so it looks like it's time to call it a day. Damn, I thought we'd sol...
- Thu Feb 02, 2006 6:29 pm
- Forum: C++ Development
- Topic: wxString::Format uint64_t problem
- Replies: 23
- Views: 6143
Google good: From here : g) Significantly incompatible with Linux C. For example, printf and scanf of standard C 64-bit %llX and %lld don't yet work, instead you have to write Microsoft C: %I64X and %I64d. Possibly this incompatibility is a natural consequence of building .exe that work without inst...