Looks like we're stuck with JMarc's hack forever ...
john
--- Begin Message ---
On Wednesday, 09. Jul 2003 13:39 John Levon wrote:
> On Wed, Jul 09, 2003 at 12:59:27PM +1000, [EMAIL PROTECTED] wrote:
>
> > > You don't agree that this is wrong ?
> >
> > In practice, no. It seems to work on all applications we've tested
> > (or had reports from).
>
> Um, I've just reported a total breakage to you.
I realize, however our customers are not having trouble (this is the
first I've heard). I don't actually see a license for you - are you
using the free edition?
> Additionally, the moving isn't recognised in other languages because
> we do not use Qt's translation system (integration issues). Yet
> another example of the "do it all in Qt or you lose" :(
>
Well, we do not have the resources to support every different possible
tool you could use to accomplish the same as we have designed
ourselves. If you use different tools you will be left to resolve these
sorts of issues. You can, of course, still just use the Qt translation
system for this one piece (ie translate the strings it looks for).
> > > > It can be via a DEFINE (if you compile Qt with
> > > > QMAC_QMENUBAR_NO_MERGE) it will be disabled.
> >
> > Unfortunetely this will be the solution you will need to use to
> > disable it.
>
> It's not a solution as already described.
>
I'm afraid it is the only solution available currently.
> > I can add it to a TODO list, however a change like this will not
> > likely to go into the 3.2.0 release (meaning it will not be changed
> > for a few releases).
>
> We really have to wait until Qt.whoknowswhen ? Binary compatibility
> issue (I could understand that ...)
>
Yes, it will not go into 3.2.x - it will appear in a later release.
Regards
//Sam
> regards
> john
>
--
Trolltech AS, Waldemar Thranes gate 98, NO-0175 Oslo, Norway
--- End Message ---
