Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Re: Making absolute point mode default

Re: Making absolute point mode default

From: Jonathan Gordon <jdgordy_at_gmail.com>
Date: Wed, 27 Oct 2010 00:28:31 +1100

On 27 October 2010 00:17, Thomas Martitz
<thomas.martitz_at_student.htw-berlin.de> wrote:
> On 26.10.2010 15:04, Jonathan Gordon wrote:
>>
>> On 26 October 2010 22:16, Thomas Martitz
>> <thomas.martitz_at_student.htw-berlin.de>  wrote:
>>>
>>> So, I'm planning to make the absolute point mode default very soon after
>>> kinetic scrolling is in.
>>> <snip>
>>
>> Amazingly I'm against this change (At least for a global change anyway).
>>
>> I have a few requirements which should at least be considered before
>> changing the default to stylus on any target (I see no reason this
>> cant be a per target descision). (in no particular order)
>> 1) the default WPS is fully touch enabled
>> 2) There should be a touch enabled sbs but I don't see this happening
>> and it isnt a totally major thing)
>> 3) if FM enabled, the FMS needs to be touch enabled (Ideally there
>> should be a standard cabbie fms, but this needs people)
>> 3a) ditto rec screen
>> 4) screens which arnt converted auto-configure themselves for grid
>> mode (with a splash saying "changed to grid mode")
>> 5) When in grid mode, a simple overlay is drawn onto the screen to
>> show the boundaries. This has two reasons, 1) it helps new people see
>> what is happening, and 2) it makes people more likely to fix those
>> screens because it will look shit. This overlay can easily be done in
>> lcd/viewport_update()
>>
>> Jonathan
>
> - I covered 1, 3, 3a and 4 with doing the change to force people to finally
> do the work needed. Neither of them applies to RaaA.

There must be a translation issue here, Forcing others to do the work
is by no means at all considered covering these issues. You mention
RaaA here but not in your first post. You specifically said you want
to do it for all touchscreen targets.
4 imo is a blocker and I will keep my vote against untill this is
done. Likewise for the skinnable screens to be touch enabled (which
can just mean changing to grid and notifiying the user).

> - 5 can be done. Sure, why not. But wouldn't you also want to draw buttons
> into the grid?

a 1 or 2 pixel grid line is far less obtrusive than trying to text
names into the areas (if that is what you mean bu drawing buttons).

There is absolutly no reason this needs to be pushed onto all touch
targets. I happen to agree than RaaA is probably ready but I'm still
against untill 4 is done (and to a lesser extent - although I tihnk it
would be very useful - 5).

http://www.rockbox.org/tracker/task/10804 should be included in any
discussion about changing the default (or cleaning up the touch
interface).
http://www.rockbox.org/tracker/task/10639 is an (unknown to me
quality) patch to add touch to the eq

Jonathan
Received on 2010-10-26


Page was last modified "Jan 10 2012" The Rockbox Crew
aaa