Re: [Development] Exposing QScreen API to QML

2011-11-22 Thread Samuel Rødal
On 11/21/2011 03:38 PM, Knoll Lars (Nokia-MP-Qt/Oslo) wrote: > On 11/21/11 12:42 PM, "Samuel Rødal" wrote: > >> On 11/21/2011 11:50 AM, Knoll Lars (Nokia-MP-Qt/Oslo) wrote: >>> On 11/21/11 10:49 AM, "ext Samuel Rødal" wrote: >>> On 11/21/2011 08:48 AM, ext Alan Alpert wrote: > The threa

Re: [Development] Exposing QScreen API to QML

2011-11-21 Thread lars.knoll
On 11/21/11 12:42 PM, "Samuel Rødal" wrote: >On 11/21/2011 11:50 AM, Knoll Lars (Nokia-MP-Qt/Oslo) wrote: >> On 11/21/11 10:49 AM, "ext Samuel Rødal" wrote: >> >>> On 11/21/2011 08:48 AM, ext Alan Alpert wrote: The thread about Window{} has progressed, and I still prefer that attached

Re: [Development] Exposing QScreen API to QML

2011-11-21 Thread Samuel Rødal
On 11/21/2011 11:50 AM, Knoll Lars (Nokia-MP-Qt/Oslo) wrote: > On 11/21/11 10:49 AM, "ext Samuel Rødal" wrote: > >> On 11/21/2011 08:48 AM, ext Alan Alpert wrote: >>> The thread about Window{} has progressed, and I still prefer that >>> attached >>> property approach compared to a Screen property

Re: [Development] Exposing QScreen API to QML

2011-11-21 Thread lars.knoll
On 11/21/11 10:49 AM, "ext Samuel Rødal" wrote: >On 11/21/2011 08:48 AM, ext Alan Alpert wrote: >> The thread about Window{} has progressed, and I still prefer that >>attached >> property approach compared to a Screen property on Window. The attached >> property allows you to access the propertie

Re: [Development] Exposing QScreen API to QML

2011-11-21 Thread Samuel Rødal
On 11/21/2011 08:48 AM, ext Alan Alpert wrote: > The thread about Window{} has progressed, and I still prefer that attached > property approach compared to a Screen property on Window. The attached > property allows you to access the properties of your current screen from any > graphical object eas

Re: [Development] Exposing QScreen API to QML

2011-11-20 Thread Alan Alpert
On Wed, 9 Nov 2011 06:17:10 Knoll Lars (Nokia-MP-Qt/Oslo) wrote: > On 11/7/11 9:21 AM, "ext Alan Alpert" wrote: > >On Wed, 2 Nov 2011 18:03:21 ext Samuel Rødal wrote: > >> Hello, > >> > >> I'm one of the guys who have been working on the Lighthouse API changes > >> for Qt 5 and new Qt 5 APIs like

Re: [Development] Exposing QScreen API to QML

2011-11-08 Thread Samuel Rødal
On 11/07/2011 09:21 AM, ext Alan Alpert wrote: > On Wed, 2 Nov 2011 18:03:21 ext Samuel Rødal wrote: >> Hello, >> >> I'm one of the guys who have been working on the Lighthouse API changes >> for Qt 5 and new Qt 5 APIs like QWindow and QScreen. For those who are >> not familiar, QWindow is the low-

Re: [Development] Exposing QScreen API to QML

2011-11-08 Thread lars.knoll
On 11/7/11 9:21 AM, "ext Alan Alpert" wrote: >On Wed, 2 Nov 2011 18:03:21 ext Samuel Rødal wrote: >> Hello, >> >> I'm one of the guys who have been working on the Lighthouse API changes >> for Qt 5 and new Qt 5 APIs like QWindow and QScreen. For those who are >> not familiar, QWindow is the low-

Re: [Development] Exposing QScreen API to QML

2011-11-07 Thread Alan Alpert
On Wed, 2 Nov 2011 18:03:21 ext Samuel Rødal wrote: > Hello, > > I'm one of the guys who have been working on the Lighthouse API changes > for Qt 5 and new Qt 5 APIs like QWindow and QScreen. For those who are > not familiar, QWindow is the low-level Qt abstraction of a native window > that has it

[Development] Exposing QScreen API to QML

2011-11-02 Thread Samuel Rødal
Hello, I'm one of the guys who have been working on the Lighthouse API changes for Qt 5 and new Qt 5 APIs like QWindow and QScreen. For those who are not familiar, QWindow is the low-level Qt abstraction of a native window that has its own rendering surface (native means whatever the Lighthouse