date:20160808

[Development] [Announce] Qt Creator 4.1 RC1 released (second attempt)

2016-08-08 Thread List for announcements regarding Qt releases and development

(Sorry for the noise. My previous mail contained an incorrect link)

We are pleased to announce the release of Qt Creator 4.1.0 RC1!

http://blog.qt.io/blog/2016/08/08/qt-creator-4-1-rc1-released/

Br, 
-- 
Alessandro Portale
Senior Manager, R

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
alessandro.port...@qt.io
+123 45 6789012
http://qt.io
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 
144331 B
___
Announce mailing list
annou...@qt-project.org
http://lists.qt-project.org/mailman/listinfo/announce
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [QML] Avoiding graphics flicker in Quick2

2016-08-08 Thread Denis Shienkov

> BUT: If I use resize(w, h+1) or resize(w, h-1), then, seems I do not see
any flickers.

Sorry, but with XCB also flickered. :(

2016-08-08 14:05 GMT+03:00 Denis Shienkov :

> > Can you try the regular xcb qpa plugin and see whether that has the same
> behavior?
>
> Yes, I have tested it with XCB and see the same issue. But only when I use
> fullScreen() or resize(w, h), where 'w' and 'h' it is native screen size.
>
> BUT: If I use resize(w, h+1) or resize(w, h-1), then, seems I do not see
> any flickers.
>
>
> 2016-08-05 20:11 GMT+03:00 Louai Al-Khanji :
>
>>
>> > On Aug 4, 2016, at 6:10 AM, Denis Shienkov 
>> wrote:
>> > > I'm going to guess you're using eglfs or something like that
>> >
>> > Yes, I use EGLFS via X11 on Linux Apalis T30 board, where are used
>> NVIDIA's drivers.
>> >
>>
>> Can you try the regular xcb qpa plugin and see whether that has the same
>> behavior?
>>
>> Cheers,
>> Louai
>>
>>
>>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] [Announce] Qt Creator 4.1 RC1 released

2016-08-08 Thread List for announcements regarding Qt releases and development

We are pleased to announce the release of Qt Creator 4.1.0 RC1!

http://blog.qt.io/blog/2016/08/08/qt-creator-4-1-rc1-released/

Br,
--
Alessandro Portale
Senior Manager, R

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
alessandro.port...@qt.io
+123 45 6789012
http://qt.io
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 
144331 B
___
Announce mailing list
annou...@qt-project.org
http://lists.qt-project.org/mailman/listinfo/announce
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] QT Touch Handling Bug

2016-08-08 Thread Rob Martens

I'm relatively sure this problem exposes a bug in qevdevtouchhandler.cpp. I
sometimes get a 0 reported from a touch event when I know the locations
from the driver never included a 0. I hope someone with experience
in QEvdevTouchScreenData::processInputEvent would look at it and see if
this isn't the case.
Thanks,
Rob

Problem Summary

Driver:

FocalTech ft5x06 TouchScreen driver.

ft5x06_ts.c

QT Code:

qevdevtouchhandler.cpp, within libQt5EglDeviceIntegration.so.5.5.0

Configuration:

type A processing (or not B type)

single touch is true

Description of problem:

When QEvdevTouchScreenData::processInputEvent gets the following (see
below) set of events an invalid touch location (always zero) is reported to
the qt Window. You can see below the full output trace (no other events
occurred).  When QT is processing the input events the second touch up
reports the y as 0, which is wrong.

The patterns seems to be the following. When QT doesn't get a ABS_Y
location after the last BTN_TOUCH Down, it reports y as 0 which is
incorrect. This always happens when y or x does not change between touches.
So if a user happens to touch in the same spot (like on a button) the
second click may not register.

Is this a problem with QT not keeping the previous Y or X location and
using that or is it a problem with the driver not reporting the X or Y
location after the touch down event? This is an annoying problem because it
means that on screens button presses are randomly missed.

QEvdevTouchScreenData::processInputEvent EV_KEY, BTN_TOUCH, 1 DOWN **
QEvdevTouchScreenData::processInputEvent EV_ABS, ABS_X, 334
QEvdevTouchScreenData::processInputEvent EV_ABS, ABS_Y, 174
QEvdevTouchScreenData::processInputEvent EV_ABS, ABS_PRESSURE, 100
QEvdevTouchScreenData::processInputEvent EV_SYN, SYN_REPORT, 0
QEvdevTouchScreenData::addTouchPoint tp.rawPositions.append(QPointF(334,
174));
QEvdevTouchScreenData::processInputEvent reportPoints()
QWindowSystemInterface::handleTouchEvent m_touchPoints.count()=1 1
x=0.695833 y=0.639706
QEvdevTouchScreenData::processInputEvent EV_KEY, BTN_TOUCH, 0   UP
QEvdevTouchScreenData::processInputEvent EV_ABS, ABS_PRESSURE, 0
QEvdevTouchScreenData::processInputEvent EV_SYN, SYN_REPORT, 0
QEvdevTouchScreenData::addTouchPoint tp.rawPositions.append(QPointF(334,
174));
QEvdevTouchScreenData::processInputEvent reportPoints()
QWindowSystemInterface::handleTouchEvent m_touchPoints.count()=1 1
x=0.695833 y=0.639706
QEvdevTouchScreenData::processInputEvent EV_KEY, BTN_TOUCH, 1 DOWN
***
QEvdevTouchScreenData::processInputEvent EV_ABS, ABS_X, 336

>> NOTICE Y not reported because it is the same
location as before
QEvdevTouchScreenData::processInputEvent EV_ABS, ABS_PRESSURE, 100
QEvdevTouchScreenData::processInputEvent EV_SYN, SYN_REPORT, 0
QEvdevTouchScreenData::addTouchPoint tp.rawPositions.append(QPointF(336, 0
));
QEvdevTouchScreenData::processInputEvent reportPoints()
QWindowSystemInterface::handleTouchEvent m_touchPoints.count()=1 1 0.70
0.00
QEvdevTouchScreenData::processInputEvent EV_KEY, BTN_TOUCH, 0   UP
QEvdevTouchScreenData::processInputEvent EV_ABS, ABS_PRESSURE, 0
QEvdevTouchScreenData::processInputEvent EV_SYN, SYN_REPORT, 0
QEvdevTouchScreenData::addTouchPoint  tp.rawPositions.append(QPointF(336, 0
));
QWindowSystemInterface::handleTouchEvent m_touchPoints.count()=1 1
x=0.70 y=0.00

DTS for ft5x06

dts

  ft5x06_ts@38 {

   compatible = "focaltech,5x06";

   reg = <0x38>;

   focaltech,family-id = <0x55>;

   pinctrl-names = "default";

   pinctrl-0 = <_pins>;

   interrupt-parent = <>;

   interrupts = <3 IRQ_TYPE_EDGE_FALLING>;

   vdd-supply = <_3v3_regulator>;

   vcc_i2c-supply = <_3v3_regulator>;

   focaltech,irq-gpio = < 3 0x00>;

   focaltech,display-coords = <0 0 480 272>;

   focaltech,name = "ft6x06";

   focaltech,no-force-update;

   focaltech,group-id = <1>;

   focaltech,hard-reset-delay-ms = <20>;

   focaltech,soft-reset-delay-ms = <150>;

   focaltech,num-max-touches = <1>;

   focaltech,fw-name = "ft_8610_qrd_fw.bin";

   focaltech,fw-delay-aa-ms = <100>;

   focaltech,fw-delay-55-ms = <30>;

   focaltech,fw-upgrade-id1 = <0x79>;

   focaltech,fw-upgrade-id2 = <0x08>;

   focaltech,fw-delay-readid-ms = <10>;

   focaltech,fw-delay-era-flsh-ms = <2000>;

   focaltech,fw-auto-cal;

   //focaltech,mirror_h;

   //focaltech,mirror_v;

   };
-- 
Rob Martens
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [QML] Avoiding graphics flicker in Quick2

2016-08-08 Thread Denis Shienkov

> Can you try the regular xcb qpa plugin and see whether that has the same
behavior?

Yes, I have tested it with XCB and see the same issue. But only when I use
fullScreen() or resize(w, h), where 'w' and 'h' it is native screen size.

BUT: If I use resize(w, h+1) or resize(w, h-1), then, seems I do not see
any flickers.


2016-08-05 20:11 GMT+03:00 Louai Al-Khanji :

>
> > On Aug 4, 2016, at 6:10 AM, Denis Shienkov 
> wrote:
> > > I'm going to guess you're using eglfs or something like that
> >
> > Yes, I use EGLFS via X11 on Linux Apalis T30 board, where are used
> NVIDIA's drivers.
> >
>
> Can you try the regular xcb qpa plugin and see whether that has the same
> behavior?
>
> Cheers,
> Louai
>
>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming...

2016-08-08 Thread Jani Heikkinen

Hi all,


Qt5.git integration in 'dev' succeed during the weekend and we have soft 
branched '5.8' from 'dev'. It means Qt 5.8 Feature Freeze will be effect 15th 
August 2016 as well as final branching from 'dev' to '5.8'


So please start using '5.8' for changes targeted to Qt 5.8 release and finalize 
ongoing ones in 'dev'. Final downmerge from 'dev' to '5.8' will happen Monday 
15th Aug (morning).


Please make sure

- All new modules for Qt 5.8 are in 'dev' & part of qt5.git

- All mandatory new features are in 'dev' now or coming in within a week?

- New feature page contains all new features etc: 
https://wiki.qt.io/New_Features_in_Qt_5.8


We will create first src packages from latest qt5.git integration as soon as 
possible. Please check the packages immediately when available to see if 
something important is missing. Those packages should be quite close to Qt 5.8 
alpha packages so it will be really important to check the packages now.



br,

Jani



Jani Heikkinen
Release Manager

The Qt Company
Elektroniikkatie 13
90590 Oulu Finland
jani.heikki...@qt.io
+358 50 4873735
http://qt.io


[http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png]
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_facebook.png]
 [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png] 
   
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png] 
  
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_googleplus.png] 
   
[http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png] 


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Johan Helsing for Approver status

2016-08-08 Thread Giulio Camuffo

+1

2016-08-06 8:31 GMT+02:00 Erik Larsson :
> +1
>
> 2016-08-04 12:22 GMT+02:00 Paul Tvete :
>>
>> Hi all,
>>
>>
>> I'd like to nominate Johan Helsing for Approver status. He joined The Qt
>> Company half a year ago, and has been working full time on Qt since. Johan
>> has been actively involved in making the QtWaylandCompositor module ready
>> for Qt 5.8, as well as doing a major part of the bug fixes for Qt Wayland in
>> 5.6 and 5.7.
>>
>> Here is his gerrit dashboard:
>>
>> https://codereview.qt-project.org/#/q/owner:%22Johan+Helsing%22,n,z
>>
>> Johan's list of reviews can be found at:
>>
>>
>> https://codereview.qt-project.org/#/q/reviewer:%22Johan+Helsing+%253Cjohan.helsing%2540theqtcompany.com%253E%22,p,003e6e7d0002807d
>>
>> Cheers,
>>
>> - Paul
>>
>>
>> ___
>> Development mailing list
>> Development@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] [Announce] Qt Creator 4.1 RC1 released (second attempt)

Re: [Development] [QML] Avoiding graphics flicker in Quick2

[Development] [Announce] Qt Creator 4.1 RC1 released

[Development] QT Touch Handling Bug

Re: [Development] [QML] Avoiding graphics flicker in Quick2

[Development] HEADS-UP: Branching from 'dev' to '5.8' ongoing, Qt 5.8 Feature Freeze coming...

Re: [Development] Nominating Johan Helsing for Approver status

7 matches

Site Navigation

Mail list logo

Footer information