Re: [AD] Touch input, new emulation mode

[Michał Cichoń <michcic@xxxxxxxxxx>]

Actually, to migrate to new API user have to call
al_install_touch_input(). Done.
That way touch input device provide one-button mouse emulation by default.

Trentg need old behavior, where distinct touches were reported as
different mouse buttons. After Trentg commit his patch another call
should be made do enable the old way:
al_set_mouse_emulation_mode(ALLEGRO_MOUSE_EMULATION_BACKWARDS_COMPATIBLE);



On 23 March 2011 20:26, Matthew Leverton <meffer@xxxxxxxxxx> wrote:
> On Wed, Mar 23, 2011 at 1:49 PM, Michał Cichoń <michcic@xxxxxxxxxxxx> wrote:
>> Deprecated doesn't mean "screwed up", but "we improved our tool basing
>> on experience we got while creating it". Better choice of words will
>> be "not recommended".
>> OK. After rethinking whole thing I can agree to this new-old emulation mode.
>>
>> But I still think this is not the best way to use mouse/touch input IMHO.
>>
>>
> Is there a comparison of the old/new APIs somewhere?
>
> I think a main goal should be that one doesn't have to write
> touch-specific code if all he wants to do is track that somebody
> clicked on (x,y). If the OS doesn't automatically do that, then I
> think Allegro should require the programmer to enable distinct touch
> events if he expects to process them. But perhaps nothing I'm saying
> is relevant to the discussion...
>
> --
> Matthew Leverton
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers



-- 
thedmd, Michał Cichoń
Artifex Mundi
michcic@xxxxxxxxxx
http://www.artifexmundi.com