Mercurial > dwindows
view dwindows1.pc.in @ 2611:ed2c4a503666
Android: Implement button release and motion notify events.
Motion notify events will always have an associate touch on Android so
button will always be masked. I currently mask button 1 for motion notify
to match the behavior I implemented on iOS. However since long touches get
interpreted as button 2, if you hold the touch long enough while moving it
could potentially be interpreted as button 2... Not sure if we should always
mask button 1 like I am doing now, or let it become button 2 after the long
touch time has passed. Whatever the behavior it should match iOS.
author | bsmith@81767d24-ef19-dc11-ae90-00e081727c95 |
---|---|
date | Sun, 18 Jul 2021 15:56:12 +0000 |
parents | 5f0e4ca14dcd |
children |
line wrap: on
line source
prefix=@prefix@ exec_prefix=${prefix} libdir=${exec_prefix}/lib includedir=${exec_prefix}/include Name: dwindows Description: Dynamic Windows Cross platform UI Toolkit Version: @VERSION@ Libs: -L${prefix}/lib -ldwindows @LIBS@ Cflags: -I${prefix}/include @CFLAGS@ -D@DW_DEFINE@