kwin/libkwineffects
Frederik Gladhorn 12886cf442 Be consistent about touch point id type: use qint32
Summary:
There is no point in using quint32 and casting back and forth in numerous places.
Fix a bunch of compiler warnings that we implicitly cast between signed and unsigned.
This makes things consistent with what we get from libinput.

Reviewers: #kwin, romangg

Reviewed By: #kwin, romangg

Subscribers: zzag, romangg, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D23086
2019-08-11 22:15:05 +02:00
..
anidata.cpp
anidata_p.h
CMakeLists.txt
kwinanimationeffect.cpp
kwinanimationeffect.h
kwinconfig.h.cmake
kwineffects.cpp Be consistent about touch point id type: use qint32 2019-08-11 22:15:05 +02:00
kwineffects.h Be consistent about touch point id type: use qint32 2019-08-11 22:15:05 +02:00
kwinglobals.h
kwinglplatform.cpp
kwinglplatform.h
kwingltexture.cpp
kwingltexture.h
kwingltexture_p.h
kwinglutils.cpp
kwinglutils.h
kwinglutils_funcs.cpp
kwinglutils_funcs.h
kwinxrenderutils.cpp
kwinxrenderutils.h
logging.cpp
logging_p.h
Mainpage.dox
Messages.sh