Hi.
The following is suggested improvement to EBookDroid. I completed my evaluation for editor of application & I like to put my ideas which may be of benefit to you.
During activation of edit mode (while in editing tools) there should be:
1) Deactivation of both left & right side bar menus because they cause problems
when user try to highlight at extreme left or right. Trying to put for ex:
underline at extreme left word (using autocrop mode) may cause left side bar
menu to be bring by user accidentally without his desire while try to put
underline.
2) Deactivation of system menu icons & options while user in handwriting. When
I used handwite tool, it is very common that accidentally touching area of
system menu (that I'm already hide it), this will bring it up to view & as a
result it will be very common to touch it's options like "Back" icon which lead
to disturb editing ..... So, it will be nice to add new option to "Disable Back
& MENU Buttons during Freehand" in such a manner that even if someone touch
area of menu & bring it up it will be functionless during handwriting.
3) Palm rejection during handwriting. when I used handwrite tool, I have
problem that I should never make my hand palm to touch screen. Otherwise it
will lead to marks on page that I does not intended. So application need to add
"Palm rejection option" as critical update.
4) Add new option: "2 finger (double finger) scrolling without causing edit"
while user in edit mode, so as to allow him or here to change from position to
other (say upper or lower one) in the page without deactivation of edit mode
then change position then enter edit mode again & finally make edition. This
option exist in ezPDF reader & very helpfull during landscape position. However
in ezPDF reader there is big bug in this option: using it lead to deactivation
"look horizontal movement option" that was previously activated by user.
5) The thinnest thickness is thick for all tools. There is need for make it
thinner than which exist now.
Best
Original issue reported on code.google.com by dr.y.j.k...@gmail.com on 21 Feb 2014 at 12:09
Original issue reported on code.google.com by
dr.y.j.k...@gmail.com
on 21 Feb 2014 at 12:09