OR this could be a result of using QRawFont "backdoor" :)
@Fan Yang: did you file a bug? what is it's number?
Konstantin
2012/11/28 Hausmann Simon :
> Hi,
>
> If the issue appears only with QtWebKit on Windows but not with the same
> version on Mac or Linux/X11, then I think it is very unlikel
Hi,
If the issue appears only with QtWebKit on Windows but not with the same
version on Mac or Linux/X11, then I think it is very unlikely that it can be
resolved with a setting. These things should work out of the box with Qt (like
you expect).
It could be an issue in WebKit, maybe ICU or som
Hi all,
I just wanted to highlight QTBUG-28011 [1]. I feel that this causes a
number of problems:
- Breaks old code, while only yielding warnings, which are then
followed by hard to interpret linker errors
- Means that source code where headers and sources are split into
different directories all
Hi,
_Translation infrastructure_
The translation infrastructure is ready for Qt 5
(http://blog.qt.digia.com/blog/2012/11/28/translation-infrastructure-ready-qt-5-0-0-string-freeze/).
We hope to see your translations moving in.
_Qt 5.0.0 string freeze_
Qt 5.0.0 string freeze has been proposed on
Any update?
On Tue, Nov 27, 2012 at 8:30 AM, Yang Fan wrote:
> Any update?
>
>
> On Fri, Nov 23, 2012 at 8:07 AM, Yang Fan wrote:
>
>> Yes, I checked this issue on Windows 7, Mac OSX 10.6.8 and Ubuntu 12.10,
>> only Windows version has this problem, so I indicated it on Windows in the
>> mail
On Tue, Nov 27, 2012 at 6:58 AM, Mark wrote:
> Hi,
>
> I just opened this feature request [1] and usually i don't open
> another question for the same stuff on the development list. Guess
> this time is different ;)
Even if this time is different, I'm still going to put my comments on
the idea in
ssh://codereview.qt-project.org:29418/qt/qtchooser.git should work now.
--
Sergio Ahumada
Quality Engineer - Digia, Qt
From: Knoll Lars
Sent: Tuesday, November 27, 2012 15:20
To: Thiago Macieira
Cc: development@qt-project.org; Ahumada Sergio
Subject: Re:
On Tue, Nov 27, 2012 at 02:03:35PM -0200, Thiago A. Corrêa wrote:
> On Tue, Nov 27, 2012 at 8:23 AM, Oswald Buddenhagen
> wrote:
> >>
> > yeah, i think it's a good idea to put it into that repo.
> > alternative naming ideas:
> > qtwrapper (that's too undescriptive)
> > qtchooser (i kinda like tha
Hi,
On Tue, Nov 27, 2012 at 8:23 AM, Oswald Buddenhagen
wrote:
>>
> yeah, i think it's a good idea to put it into that repo.
> alternative naming ideas:
> qtwrapper (that's too undescriptive)
> qtchooser (i kinda like that)
> qtswitcher
> qtdispatcher
> qt-version-manager (j/k)
>
Gentoo has a to
> -Original Message-
> [mailto:development-bounces+tvaneerd=rim@qt-project.org] On Behalf
> Of Ziller Eike
>
> On 23 Nov 2012, at 11:20, Peter Hartmann wrote:
>
> >> Do you intend to upgrade this version of Qt that's installed on the
> device
> >> without upgrading the applications u
Hi,
I just opened this feature request [1] and usually i don't open
another question for the same stuff on the development list. Guess
this time is different ;)
Considering that QtQuick 2.0 is very different compared to 1.1 i'm
wondering if this late header change could be added by someone to the
> From: Lukas Geyer
> Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
> Am 27.11.2012 11:03, schrieb Sascha Cunz:
>> [...]
>>> The difference is that 'operate' and 'configure' are
> two different tasks
>>> and thus usually require two different interfaces.
>>> The
qtchooser is ok for me. Sergio, can you help to create the repo, please?
Thanks,
Lars
On Nov 27, 2012, at 3:12 PM, Thiago Macieira wrote:
> On terça-feira, 27 de novembro de 2012 11.23.00, Oswald Buddenhagen wrote:
>> qtchooser (i kinda like that)
>> qtswitcher
>
> I like those two.
>
> So r
On terça-feira, 27 de novembro de 2012 11.23.00, Oswald Buddenhagen wrote:
> qtchooser (i kinda like that)
> qtswitcher
I like those two.
So requesting it as qtchooser. I'll rename the tool to match the repository
name.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - I
Hi
We had some concerns to discuss moderation part there that's why we made it
private but after discussion we agreed to make it public.
I have already send request to make it public and open for all and will be
fixed soon.
I will update you all as soon this is public :)
Thank you for all dis
Am 27.11.2012 11:03, schrieb Sascha Cunz:
> [...]
>> The difference is that 'operate' and 'configure' are two different tasks
>> and thus usually require two different interfaces.
>>
>> The 'operate' interface of an anti-malware service is to monitor data
>> and network traffic. The 'configure' int
On 27/11/12 8:03 PM, Sascha Cunz wrote:
>> Qt already allows to serialize any datatype known to the meta type
>> system, provides means for IPC (D-Bus is just one example) and has a
>> code generator which implements our objects (moc) and allows for
>> handling asynchronous signals and slots.
>>
>>
On Tuesday 27 November 2012 10:03:11 Nurmi J-P wrote:
> > >> We agreed that the tool wrapper wouldn't live inside qtbase.git nor
> > >> qt.git (Qt 4), so I need a new repository for it. I think it should be
> > >> in the qt/>
> > hierarchy.
> >
> > > Isn't qttools suitable, regardless of its depe
23.11.2012, 14:07, "Peter Hartmann" :
> This situation is different on mobile (and I guess embedded as well);
On embedded you usually can rebuild all software when changing Qt, so
binary compatibility is not important.
--
Regards,
Konstantin
___
Deve
On Tuesday 27 November 2012 11:23:00 Oswald Buddenhagen wrote:
> On Tue, Nov 27, 2012 at 11:04:45AM +0100, Olivier Goffart wrote:
> > On Tuesday 27 November 2012 10:40:57 Simon Hausmann wrote:
> > > On Monday, November 26, 2012 10:54:54 PM Thiago Macieira wrote:
> > > > We agreed that the tool wrap
On 23 Nov 2012, at 14:15, Rutledge Shawn wrote:
>
> On 23 Nov 2012, at 11:07 AM, Peter Hartmann wrote:
>
>> On 11/23/2012 12:12 AM, André Pönitz wrote:
>>> (...)
>>> The reality is that this guarantee often enough does not hold in
>>> practice. Vendors of "binary" Qt based application typicall
On 23 Nov 2012, at 11:20, Peter Hartmann wrote:
> On 11/23/2012 11:11 AM, Poenitz Andre wrote:
>> Peter Hartmann wrote:
>>> On 11/23/2012 12:12 AM, André Pönitz wrote:
(...)
The reality is that this guarantee often enough does not hold in
practice. Vendors of "binary" Qt based app
On 2012/11/27 12:23 PM, Oswald Buddenhagen wrote:
> yeah, i think it's a good idea to put it into that repo.
> alternative naming ideas:
> qtwrapper (that's too undescriptive)
> qtchooser (i kinda like that)
> qtswitcher
> qtdispatcher
> qt-version-manager (j/k)
qtver ?
--
Regards
Alex
On Tue, Nov 27, 2012 at 11:04:45AM +0100, Olivier Goffart wrote:
> On Tuesday 27 November 2012 10:40:57 Simon Hausmann wrote:
> > On Monday, November 26, 2012 10:54:54 PM Thiago Macieira wrote:
> > > We agreed that the tool wrapper wouldn't live inside qtbase.git nor qt.git
> > > (Qt 4), so I need
On Tuesday 27 November 2012 10:40:57 Simon Hausmann wrote:
> On Monday, November 26, 2012 10:54:54 PM Thiago Macieira wrote:
> > Hello
> >
> > We agreed that the tool wrapper wouldn't live inside qtbase.git nor qt.git
> > (Qt 4), so I need a new repository for it. I think it should be in the qt/
>
[...]
> The difference is that 'operate' and 'configure' are two different tasks
> and thus usually require two different interfaces.
>
> The 'operate' interface of an anti-malware service is to monitor data
> and network traffic. The 'configure' interface is most probably a
> seperate application
> >> We agreed that the tool wrapper wouldn't live inside qtbase.git nor
> >> qt.git (Qt 4), so I need a new repository for it. I think it should be in
> >> the qt/
> hierarchy.
> >>
> >
> > Isn't qttools suitable, regardless of its dependency to qtbase?
>
> The goal was to not have any Qt depend
On Nov 27, 2012, at 10:32 AM, Nurmi J-P wrote:
>> -Original Message-
>> From: development-bounces+jpnurmi=digia@qt-project.org
>> [mailto:development-bounces+jpnurmi=digia@qt-project.org] On
>> Behalf Of Thiago Macieira
>> Sent: 27. marraskuuta 2012 7:55
>> To: development@qt-pro
On Monday, November 26, 2012 10:54:54 PM Thiago Macieira wrote:
> Hello
>
> We agreed that the tool wrapper wouldn't live inside qtbase.git nor qt.git
> (Qt 4), so I need a new repository for it. I think it should be in the qt/
> hierarchy.
Maybe this is the long awaited return of a now public de
> -Original Message-
> From: development-bounces+jpnurmi=digia@qt-project.org
> [mailto:development-bounces+jpnurmi=digia@qt-project.org] On
> Behalf Of Thiago Macieira
> Sent: 27. marraskuuta 2012 7:55
> To: development@qt-project.org
> Subject: [Development] repository for the too
Hi Lorn,
On Nov 27, 2012, at 10:18 AM, Lorn Potter wrote:
> Hi,
> Since modules/add-ons were 'removed' from qt.pro the documentation is missing
> from qt-project.org
> meaning no one can even find out about them. Do a search for one of their
> classes and they show up in the results, but the d
Am 27.11.2012 08:50, schrieb Sascha Cunz:
>> Yes. Each service which needs to interact with the user requires some
>> sort of IPC to provide a graphical interface, as interactive services
>> are not allowed on most modern operating systems (not to mention design
>> considerations).
> As you said: t
Hi,
Since modules/add-ons were 'removed' from qt.pro the documentation is missing
from qt-project.org
meaning no one can even find out about them. Do a search for one of their
classes and they show up in the results, but the documents are missing.
I know it was easiest to just remove these modul
Hello
We agreed that the tool wrapper wouldn't live inside qtbase.git nor qt.git
(Qt 4), so I need a new repository for it. I think it should be in the qt/
hierarchy.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
34 matches
Mail list logo
