Op 12 okt. 2011, om 20:34 heeft Simon Busch het volgende geschreven: > On 12.10.2011 20:14, Koen Kooi wrote: >> >> >> Op 12 okt. 2011 om 20:10 heeft Simon Busch <morp...@gravedo.de> het volgende >> geschreven: >> >>> On 12.10.2011 10:02, Eric Bénard wrote: >>>> Hi, >>>> >>>> Le 12/10/2011 09:45, Martin Jansa a écrit : >>>>> From: Simon Busch<morp...@gravedo.de> >>>>> >>>>> In most cases we don't need tslib in std. configuration as touchscreen >>>>> access in most >>>>> devices today is done with linux input interface. If some specific >>>>> machine has a need for >>>>> tslib support it should add the dependency in it's machine layer again >>>>> and modify the >>>>> profile script accordingly. >>>>> >>>> When using a resistive touchscreen, tslib is a common solution to handle >>>> calibration and raw value processing : do you think this is a good thing >>>> to remove this ? >>> >>> Thats up to the environment you are using qt4-embedded in. In my case >>> the setup is a little bit more complicated. We're using tslib but not >>> directly in qt4-embedded (we can get rid of tslib completely but time is >>> missing). >>> >>> I removed the dependency from qt4-embedded as qt4-embedded in oe-core >>> should be the general thing used in all environments and therefore >>> should be only a minimal setup with minimal dependencies. >> >> No, it should work in most cases, breaking qt:e like is not acceptable. > > What is breaking qt:e in this case? For me it's just a feature reduction > and not a break (as qt:e still works fine with the linux input interface).
When your TS is suddenly uncalibrated and jittery, it's a breakage, not a feature reduction. _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core