"dragging" and "flicking" touch reaction in 1.4.0-dev-r1012 is worst than in 1.4.0-dev-r991

[GoogleCodeExporter]

I must say the the touch experience in the older version 1.4.0-dev-r991 was 
PERFECT. When you touch the screen in r991 the page movement response and the 
scrolling fluidness is just Perfect.

In r1012 scrolling fluidness appears to be the same as before "AT the END". The 
problem is that the touch reaction when you flick (drag) is bad. The page first 
start "moving" then stop and only then start moving/scrolling fluid.

Some of the changes you made from r991 to r1012 appears to deteriorate 
something again.
In this last release(r1012) the scrolling/touch response is not as bad as in 
older releases like 1.3.2(which was unusable for djvu to me), but is bad in 
comparison to r991
R991 is the best release so far, it has some bugs but the reading experience is 
very good, very comfortable, those bugs could be fixed or not but it was a good 
release.

This is just an opinion but
"What is the purpose to have the most spectacular ebook reader app with any 
customizable option you can imaging if it fails to do in a perfect way the very 
first task it should do: render ebooks correctly to have a good reading 
experience?"

Original issue reported on code.google.com by lanos...@gmail.com on 6 Mar 2012 at 12:38

[GoogleCodeExporter]

Я уже в течении многих релизов программы не 
видел такой плавной, гладкой и непрерывной 
прокрутки (скролинга) страниц как в 
ebookdroid-1.4.0-dev-r1007.apk . В версии же 
ebookdroid-1.4.0-dev-r1012.apk опять начинает теряться 
плавность в прокрутке. Она опять начинает 
идти рывками (если быть ещё немного 
честнее, то это становится особенно 
заметно на стыке страниц, когда видимо 
начинает декодироваться "следующая" 
страница).

Original comment by Original...@gmail.com on 6 Mar 2012 at 5:16

[GoogleCodeExporter]

следует заметить,  что в 1007 это достигалось 
за счет полной неработоспособности при 
зуме большем 2.0

Original comment by Alexander.V.Kasatkin@gmail.com on 6 Mar 2012 at 6:20

[GoogleCodeExporter]

Reading what Original...@gmail.com said, i tried 1.4.0-dev-r1007 and it is also 
Perfect, it is perfect as version 1.4.0-dev-r991. I agree with him, these 
versions are the best of many releases, and in my opinion they are the best of 
all.

Regarding about you said Alexander, that the smoothness in release r1007 was 
achieved without "enabling larger 2.0 zoom" is exactly about i was talking 
about before.
What is the purpose to add a "zoom enhancement" if it will brake the perfection 
you have achieved till now?
Obviously that these are development releases, so you are trying, and it is 
okay of course, but if enabling "zoom larger than 2.0" generates a conflict and 
is a "step back", in my opinion it should be disabled, unless you can solve the 
issue and both, "enabling zoom larger 2.0" and the "smoothness achieved in 
r1007" can be accomplished together.
I said this because version 1.2.2 was smother that 1.3.2, and 1.3.2 is a 
featured version, for me 1.3.2 was a step back, even if it has superior 
customization.

Thanks for all of course, i'm very happy with releases r991 or r1007 and 
besides some minor bugs they have, which i can live with, they are very useful 
and comfortable for reading.
I must say that i'm studying, reading books using this app(a lot) and when it 
is not smooth is very very annoying to read, specially when you are reading a 
lot going back and forward within a book. In this aspect r991 or r1007 are 
perfect.

Original comment by lanos...@gmail.com on 6 Mar 2012 at 9:00

[GoogleCodeExporter]

Try r1032 - it allow to change in preferences touch processing delay value:
it was 16 mills in 1007 and 50 mills in 1012.

Original comment by Alexander.V.Kasatkin@gmail.com on 12 Mar 2012 at 8:32

• Changed state: Started

[GoogleCodeExporter]

Спасибо. Довольно хорошо работает.

Original comment by Original...@gmail.com on 12 Mar 2012 at 11:32

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It is SOLVED the problem for me too. Setting the value to 16 or less solved the 
problem.
Thanks again

PS:I also set the touch processing delay value to 1 mills, just to see...
And i think it is a little better but not too much so i ask you:
What if I set the value to lower values(for example 1 mills)? What will this 
cause? Could it use more cpu and drain more the battery or something using 
lower values of the touch response delay?
There must be a reason why longer touch delay response is better but i don't 
know hat it is

Thanks

Original comment by lanos...@gmail.com on 12 Mar 2012 at 9:33

[GoogleCodeExporter]

Yes. Lesser values gives more smooth scrolling but only until cpu can handle 
all events. Also more processing - more battery drain. So now its up to you to 
decide what do you want.

Original comment by Andrei.K...@gmail.com on 13 Mar 2012 at 5:05

• Changed state: Fixed