Attachment 13210 Details for Bug 13731 – one more correction with width calculation

[patch] one more correction with width calculation

xf86Elo.c.diff (text/plain), 1.39 KB, created by Jaroslaw Siebert on 2007-12-19 01:13:02 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Jaroslaw Siebert

Created: 2007-12-19 01:13:02 UTC

Size: 1.39 KB

patch

obsolete

>716a717
>>   /*
>717a719,721
>>   */
>>   int		width = priv->max_x - 424;
>>   /*
>718a723,724
>>   */
>>   int		height = priv->max_y - 524;
>734a741,748
>> 
>> /********** BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG ******/
>>   /*
>>   priv->min_x works fine, but the config option MIN_X > 0 doesn't 
>>   allow to change position of Pointer to < MIN_X
>>   maybe it is an option name conflict ?
>>   I put my real MIN_X here, and in xorg.conf I set up Option "MIN_X"
>>   as "0". The same with MIN_Y/
>737a752
>>   */
>738a754,756
>>   *x = (priv->screen_width * (input_x - 424)) / width;
>>   *y = (priv->screen_height -
>> 	(priv->screen_height * (input_y - 524)) / height);
>858a877,880
>> 
>> 
>> /********** BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG ******/
>>    /* It should be x and y (not cur_x, cur_y) 
>859a882,883
>>     */
>>     xf86PostMotionEvent(local->dev, TRUE, 0, 2, x, y);
>864a889,890
>> /********** BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG ******/
>>    /* It should be x and y (not cur_x, cur_y) 
>865a892,893
>>       */
>>       xf86PostButtonEvent(local->dev, TRUE, 1, state == ELO_PRESS, 0, 2, x, y);
>867a896,897
>> /********** BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG ******/
>>    /* It should be x and y (not cur_x, cur_y) 
>870a901,904
>> 		  */
>>     DBG(3, ErrorF("TouchScreen: x(%d), y(%d), %s\n",
>> 		  x, y,
>> 		  (state == ELO_PRESS) ? "Press" : ((state == ELO_RELEASE) ? "Release" : "Stream")));

Actions: View | Splinter Review

Attachments on bug 13731: 13208 | 13209 | 13210 | 13214 | 13248

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.