[muscle] Re: MUSCLE and compiler issues
- From: "Mika Lindqvist" <linki@xxxxxxx>
- To: <muscle@xxxxxxxxxxxxx>
- Date: Wed, 27 Aug 2003 06:50:00 +0300
QMessageTransceiverThread.cpp still uses QEvent::MaxUser which wasn't
defined in Qt 2.3.
> -----Original Message-----
> From: muscle-bounce@xxxxxxxxxxxxx
> [mailto:muscle-bounce@xxxxxxxxxxxxx] On Behalf Of Jeremy Friesner
> Sent: Tuesday, August 26, 2003 7:08 PM
> To: muscle@xxxxxxxxxxxxx
> Subject: [muscle] Re: MUSCLE and compiler issues
>
>
> Hi Mika,
>
> > I just wanted to know what is your opinion of adding (optional)
> > "parent" parameter to QAcceptSocketsThread and
> > QMessageTransceiverThread, because I have had odd crash issues with
> > VC6/Qt 2.3 and it would be more consistent with the other code if I
> > could pass it with the constructors. It would change the
> order of the
> > destruction of the classes, but I think normally with Qt it
> should be
> > reversed anyways (childs after parent).
>
> I think that is a good idea. I've made the changes and they
> will be in the next release -- in the meantime I'll send you
> the changed files so you can test/use them.
- Follow-Ups:
- [muscle] Re: MUSCLE and compiler issues
- From: Jeremy Friesner
- References:
- [muscle] Re: MUSCLE and compiler issues
- From: Jeremy Friesner
Other related posts:
- » [muscle] MUSCLE and compiler issues
- » [muscle] Re: MUSCLE and compiler issues
- » [muscle] Re: MUSCLE and compiler issues
- » [muscle] Re: MUSCLE and compiler issues
- » [muscle] Re: MUSCLE and compiler issues
- [muscle] Re: MUSCLE and compiler issues
- From: Jeremy Friesner
- [muscle] Re: MUSCLE and compiler issues
- From: Jeremy Friesner