Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Welcome to the Rockbox Technical Forums!

+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  Hardware
| | |-+  Gigabeat "Plus Touch" convert to real buttons
« previous next »
  • Print
Pages: [1]

Author Topic: Gigabeat "Plus Touch" convert to real buttons  (Read 2387 times)

Offline johnson4

  • Member
  • *
  • Posts: 62
Gigabeat "Plus Touch" convert to real buttons
« on: April 26, 2008, 01:26:08 AM »
Has it crossed anyone else's mind to get rid of the plus touch and replace it with 5 real buttons with some feedback? I love the gigabeat with RB but the "Plus" currently servers no other purpose. Can anyone comment from a hardware/software stand point whether it would be at all possible?
Logged

Offline markun

  • Developer
  • Member
  • *
  • Posts: 462
Re: Gigabeat "Plus Touch" convert to real buttons
« Reply #1 on: April 26, 2008, 07:58:37 AM »
The touchpad consists of 13 separate buttons of which we only check 5. I'm sure you could replace it with 5 real buttons. Good luck.
Logged

Offline Mad Cow

  • Member
  • *
  • Posts: 445
Re: Gigabeat "Plus Touch" convert to real buttons
« Reply #2 on: May 03, 2008, 02:27:48 PM »
A bit off topic here, but why does rockbox only use 5 of them? Developer choice or some software limitation?
Logged
iRiver H10 5GB, Gigabeat F40, Gigabeat S60, all rockboxed. :P

Offline GodEater

  • Member
  • *
  • Posts: 2829
Re: Gigabeat "Plus Touch" convert to real buttons
« Reply #3 on: May 06, 2008, 05:04:19 AM »
Developer choice really. No-one's bothered to do anything else with them.

Really the only sensible choice is to implement some sort of "drag" interface on them, since they're too close together to assign individual button pushes to.
Logged

Read The Manual Please

Offline Mad Cow

  • Member
  • *
  • Posts: 445
Re: Gigabeat "Plus Touch" convert to real buttons
« Reply #4 on: May 10, 2008, 12:49:53 PM »
Quote from: GodEater on May 06, 2008, 05:04:19 AM
Developer choice really. No-one's bothered to do anything else with them.

Really the only sensible choice is to implement some sort of "drag" interface on them, since they're too close together to assign individual button pushes to.

I think it would be better just to have all the buttons on each part do the same function. It's sometimes annoying how only the outer sensors do anything, I have a case for mine that makes reaching those outer ones difficult, and the others do nothing, so I have a really hard time using it in the case.
Logged
iRiver H10 5GB, Gigabeat F40, Gigabeat S60, all rockboxed. :P

Offline Llorean

  • Member
  • *
  • Posts: 12931
Re: Gigabeat "Plus Touch" convert to real buttons
« Reply #5 on: May 10, 2008, 03:04:29 PM »
I'd say enable most, not al so there is a gap between center and directions. Otherwise ite may become very easy to accidentaly hit the wrong function. I also have no problems with the default setup so I'm not sure it's a good idea to change it for imperfect cases unless it doesn't interfere at with non-case use.
Logged

Offline Mad Cow

  • Member
  • *
  • Posts: 445
Re: Gigabeat "Plus Touch" convert to real buttons
« Reply #6 on: May 10, 2008, 11:07:38 PM »
Yea I'd be for making the 2 outer pads work and leaving the inner one. But it doesn't really matter anyway, I rarely use the case because it makes my brick even bigger. :D
Logged
iRiver H10 5GB, Gigabeat F40, Gigabeat S60, all rockboxed. :P

  • Print
Pages: [1]
« previous next »
+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  Hardware
| | |-+  Gigabeat "Plus Touch" convert to real buttons
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.091 seconds with 15 queries.