On 12/06/2012 08:00 PM, Arunprasad Rajkumar wrote:
> Hello Developers,
>
> I'm new to QT. Basically I understood like QWS/QPA reduces porting QT to
> custom embedded devices without touching the core functionality of
> QtGui. Also it is a architectural split down of functionality and
> porting laye
On Dec 6, 2012, at 10:34 PM, Stephen Chu wrote:
> Trying to build RC1 using macx-clang-libc++-32 and got these errors.
> It's probably more to do with different struct sizes in 32-bit API:
>
> redefinition with different types ('struct _NSPoint' vs 'struct
> CGPoint')
> } NSPoint;
I th
Congratulations!
Any update on https://bugreports.qt-project.org/browse/QTWEBKIT-383 and
https://bugreports.qt-project.org/browse/QTBUG-28412 ?
On Fri, Dec 7, 2012 at 5:21 AM, Mark wrote:
> On Thu, Dec 6, 2012 at 5:14 PM, Tanilkan Sinan
> wrote:
> > Gratulerer.
> >
> > Knallbra jobba.
> >
> >
Hi All,
I'm trying building Qt5 from Git on Mac OS X 10.8.2, but it fails. I used
the following configure:
./configure -developer-build -opensource -confirm-license -openssl -icu
-nomake tests -nomake demos -nomake examples -platform macx-clang
And my clang version is:
Yang-FanmatoMac-mini:qt5 ya
Trying to build RC1 using macx-clang-libc++-32 and got these errors.
It's probably more to do with different struct sizes in 32-bit API:
In file included from platform/qt/WebCoreSystemInterface.mm:28:
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:37:
On Thu, Dec 6, 2012 at 5:14 PM, Tanilkan Sinan wrote:
> Gratulerer.
>
> Knallbra jobba.
>
> Sinan
>
> From: announce-bounces+sinan.tanilkan=digia@qt-project.org
> [announce-bounces+sinan.tanilkan=digia@qt-project.org] on behalf of List
> for annou
Hello Developers,
I'm new to QT. Basically I understood like QWS/QPA reduces porting QT to
custom embedded devices without touching the core functionality of QtGui.
Also it is a architectural split down of functionality and porting layer.
QWS is a legacy model & have some limitation, so we can't f
> If we're successful, this will be a non-issue once a few dozen entries
> have been added (unless everyone tries to append instead of inserting
> entries in some sorted order).
If you sort by bug ID, the recently reported bugs will be appended at the end.
So staging conflicts happen mostly for th
On Thursday 06 December 2012 17:58:57 shane.kea...@accenture.com wrote:
> > Hi Lars,
> >
> > On Monday December 3 2012, Knoll Lars wrote:
> > > Dev:
> > >
> > > Dev is the branch where you can land anything that's supposed to go
> > > into 5.1. The following policies apply:
> > >
> > > * Changes
On Thursday December 6 2012, shane.kea...@accenture.com wrote:
> > On Monday December 3 2012, Knoll Lars wrote:
> > > Dev:
> > >
> > > Dev is the branch where you can land anything that's supposed to go
> > > into 5.1. The following policies apply:
> > >
> > > * Changes have to be source and binary
> Hi Lars,
>
> On Monday December 3 2012, Knoll Lars wrote:
> > Dev:
> >
> > Dev is the branch where you can land anything that's supposed to go
> > into 5.1. The following policies apply:
> >
> > * Changes have to be source and binary compatible
> > * You can add new method and classes given that
Hi Lars,
On Monday December 3 2012, Knoll Lars wrote:
> Dev:
>
> Dev is the branch where you can land anything that's supposed to go into
> 5.1. The following policies apply:
>
> * Changes have to be source and binary compatible
> * You can add new method and classes given that they are fully docu
Gratulerer.
Knallbra jobba.
Sinan
From: announce-bounces+sinan.tanilkan=digia@qt-project.org
[announce-bounces+sinan.tanilkan=digia@qt-project.org] on behalf of List
for announcements regarding Qt releases and development
[annou...@qt-project.or
Hi,
We are happy to announce that the release candidate for Qt 5.0 has just been
released.
More information about the release can be found in Lars' blog post:
http://blog.qt.digia.com/blog/2012/12/06/qt-5-0-release-candidate/ and at
http://qt-project.org/
You can download it from: http://qt-
Hi all,
Can we start building the PostgreSQL plugin in our binary packages again by
default?
We used to do this before, but stopped doing it at some point. Was there a good
reason for that, and is it still relevant?
Thanks.
Best regards
Nils Christian Roscher-Nielsen
Sales Engineer - Digia, Q
Il 05/12/2012 19.44, Robert Knight ha scritto:
> All modeless dialogs disappear behind the main application whenever
> the user clicks outside them (consider a Find/Replace dialog which
> always needs to be on top of the main application window).
Set the window type to Qt::Tool in the QDialog o
16 matches
Mail list logo
