On 16 October 2012 10:43, Sorvig Morten wrote:
>
> On Oct 15, 2012, at 9:06 PM, Lorn Potter wrote:
>>
>> The question should really be whether there is a use case for
>> brightness/contrast getter without a setter, if that belongs in QScreen, and
>> if it needs to be exposed to qml.
>
> As a pl
On Oct 15, 2012, at 9:06 PM, Lorn Potter wrote:
>
> The question should really be whether there is a use case for
> brightness/contrast getter without a setter, if that belongs in QScreen, and
> if it needs to be exposed to qml.
As a platform developer I'm leaning towards "no": If it's in QtB
On 15/10/2012, at 6:23 PM, Samuel Rødal wrote:
> On 10/12/2012 10:24 PM, Shawn Rutledge wrote:
>> On 12 October 2012 21:03, Lorn Potter wrote:
>>> On 13/10/2012, at 12:47 AM, Shawn Rutledge
>>> wrote:
>>>
I got started working on QScreen, its properties, notifiers, and
implementati
On 10/12/2012 10:24 PM, Shawn Rutledge wrote:
> On 12 October 2012 21:03, Lorn Potter wrote:
>> On 13/10/2012, at 12:47 AM, Shawn Rutledge
>> wrote:
>>
>>> I got started working on QScreen, its properties, notifiers, and
>>> implementation on all 3 platforms after I noticed that the
>>> document
On 12 October 2012 21:03, Lorn Potter wrote:
> On 13/10/2012, at 12:47 AM, Shawn Rutledge wrote:
>
>> I got started working on QScreen, its properties, notifiers, and
>> implementation on all 3 platforms after I noticed that the
>> documentation was out of sync with the implementation in Qt5.
>
>
On 13/10/2012, at 12:47 AM, Shawn Rutledge wrote:
> I got started working on QScreen, its properties, notifiers, and
> implementation on all 3 platforms after I noticed that the
> documentation was out of sync with the implementation in Qt5.
[on a side note]
While getting reacquainted with qsys
