Be consistent about touch point id type: use qint32
12886cf442fe
Actions

Authored by gladhorn on Aug 11 2019, 7:57 PM.

Description

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

Details

Committed

gladhorn

Aug 11 2019, 8:15 PM

Reviewer

KWin

Differential Revision

D23086: Be consistent about touch point id type: use qint32

Parents

R108:ed4a9d756aab: Clean up usage of m_client

Branches

Unknown

Tags

Unknown

gladhorn committed R108:12886cf442fe: Be consistent about touch point id type: use qint32 (authored by gladhorn).Aug 11 2019, 8:15 PM

bshah mentioned this in R108:2bf2a04f8660: Fix the build error in hwcomposer backend.Aug 17 2019, 10:56 AM

Changes (20)

				Path	Packages
	M			debug_console.cpp
	M			debug_console.h
	M			effects.cpp
	M			effects.h
	M			effects/presentwindows/presentwindows.cpp
	M			effects/presentwindows/presentwindows.h
	M			effects/touchpoints/touchpoints.cpp
	M			effects/touchpoints/touchpoints.h
	M			input.cpp
	M			input.h
	M			input_event_spy.cpp
	M			input_event_spy.h
	M			libkwineffects/kwineffects.cpp
	M			libkwineffects/kwineffects.h
	M			plugins/platforms/drm/drm_inputeventfilter.cpp
	M			plugins/platforms/drm/drm_inputeventfilter.h
	M			touch_hide_cursor_spy.cpp
	M			touch_hide_cursor_spy.h
	M			touch_input.cpp
	M			touch_input.h