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
translations translations
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
|-+  Rockbox General
| |-+  Announcements
| | |-+  BUTTON CHANGES - REPORT PROBLEMS HERE
« previous next »
  • Print
Pages: 1 ... 12 13 [14]

Author Topic: BUTTON CHANGES - REPORT PROBLEMS HERE  (Read 120107 times)

Offline slash14

  • Member
  • *
  • Posts: 5
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #195 on: December 03, 2006, 01:41:08 PM »
Might sound as a stupid question but isn't it a declaration (at the very beginning of the file) ?
Code: [Select]
enum {
    METRONOME_PLAY_TAP = LAST_PLUGINLIB_ACTION+1,
#if CONFIG_KEYPAD == ONDIO_PAD
    METRONOME_PAUSE,
#endif
#if (CONFIG_KEYPAD == IRIVER_H100_PAD) || (CONFIG_KEYPAD == IRIVER_H300_PAD)
    METRONOME_SYNC
#endif
};
Without proper declaration, I think that compilation would not succeed, is it ?
Logged

Offline Mmmm

  • Developer
  • Member
  • *
  • Posts: 920
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #196 on: December 03, 2006, 03:27:07 PM »
For an #ifdef to trigger, it must have been #define 'd first.
With the new button code for plugins you can't do this as it is using a button that is specific to one set of players only (ie the record button doesn't have a general keymap).
You could give it a general keymap and call it BUTTON_RECORD or something

or you could use
#if (CONFIG_KEYPAD == IRIVER_H100_PAD) || (CONFIG_KEYPAD == IRIVER_H300_PAD)
instead of the #ifdef but that would make adding this functionality to other players, if you wanted to, a real pain.

or you could have something like
#if (CONFIG_KEYPAD == IRIVER_H100_PAD) || (CONFIG_KEYPAD == IRIVER_H300_PAD)
#define MET_SYNC
#endif
at the beginning and then have lots of #ifdef MET_SYNC instead.

Not being too familiar with (and being too lazy to look at) the Plugin button system I think I'll leave it to JDGordon who I'm sure will really enjoy deciding which is best :D ;)
Logged
My H120 build with Recording Enhancements Pack
Some examples of recordings done on H140 with Rockbox

Offline JdGordon

  • Member
  • *
  • Posts: 1817
  • Constantly breaking stuff
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #197 on: December 03, 2006, 07:35:18 PM »
? I thought #ifdef worked for all names in the file, so enum and function names and such...
ok, ill fix that then
Logged


Using PMs to annoy devs about bugs/patches is not a good way to have the issue looked at.

Offline Genre9mp3

  • Artist
  • Member
  • *
  • Posts: 146
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #198 on: December 30, 2006, 05:18:34 AM »
A minor problem I noticed yesterday. In the menu of VU Meter plugin, Up acts like Down and vice versa. Everything else seems OK. Tested on H300.
Logged

Offline JdGordon

  • Member
  • *
  • Posts: 1817
  • Constantly breaking stuff
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #199 on: December 30, 2006, 10:01:19 PM »
just checked the code for that menu and its using a custom menu, which means that the button changes of 6 months ago had no effect on them. BUT it does look like up/down are switched which is odd...
Logged


Using PMs to annoy devs about bugs/patches is not a good way to have the issue looked at.

Offline nls

  • Developer
  • Member
  • *
  • Posts: 460
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #200 on: January 02, 2007, 08:27:40 AM »
I have found a minor annoyance in the WPS context menu. If I press right on the reshuffle playlist item in the menu it just goes back to the WPS and does not reshuffle, works fine if I press NAVI though...
Logged

Offline JdGordon

  • Member
  • *
  • Posts: 1817
  • Constantly breaking stuff
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #201 on: January 09, 2007, 10:34:20 PM »
nls: ok thats wierd.. I seem to be getting the opposite here (h300). righ works, navi doesnt..

actually.. no, i tihnk both work, but for some reason its more instant with right!
Logged


Using PMs to annoy devs about bugs/patches is not a good way to have the issue looked at.

Offline nls

  • Developer
  • Member
  • *
  • Posts: 460
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #202 on: January 11, 2007, 05:50:38 AM »
Yes you're right both works for me now but it takes a good 10 seconds for the wps nex song and the playlist viewer to update even with a playlist of about 15 tracks... guess it's not a button problem then!  ;)
Logged

Offline roolku

  • Developer
  • Member
  • *
  • Posts: 349
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #203 on: January 11, 2007, 10:21:26 AM »
Following on from our discussion on IRC regarding button presses being eaten after exiting certain plugins I have done more experiments.

A plugin only containing:

Code: [Select]
while (rb->button_get(false) != BUTTON_OFF);is okay

Code: [Select]
   while (rb->button_get(false) != (BUTTON_OFF | BUTTON_REL));is not okay

Code: [Select]
while (rb->button_get(false) != BUTTON_OFF);
rb->splash(HZ/3, true, "Bye now!");
is not okay for a short press

Code: [Select]
while (rb->button_get(false) != BUTTON_OFF);
rb->splash(HZ/3, true, "Bye now!");
is okay if I hold the button long enough for the splash to disappear

So I am guessing that there needs to be a button code in the queue (i.e. the button release) when exiting the plugin that is then eaten by the action code. If there isn't a "victim" left, the action code will eat the next intentional press available.

I tried to 'repair' calculator.rock by removing the splash screen at the end and it 'fixed' it. However this is not the correct way of solving it, it needs to be fixed outside the plugin.

EDIT:

I found a call to button_clear_queue(); in plugin_load(); immediately after the plugin returns. Removing it fixed the problem for the vast majority of plugins. Some (including the calculator) still have the problem though. Also this call was probably there for a reason, so I don't know what side-effect its removal will have on other targets.



« Last Edit: January 11, 2007, 11:56:52 AM by roolku »
Logged

Offline JdGordon

  • Member
  • *
  • Posts: 1817
  • Constantly breaking stuff
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #204 on: March 31, 2007, 08:18:07 PM »
fix committed
Logged


Using PMs to annoy devs about bugs/patches is not a good way to have the issue looked at.

Offline tspoon

  • Member
  • *
  • Posts: 96
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #205 on: October 14, 2007, 03:19:21 AM »
 I know I posted this exact same problem here earlier - and I'm sure it was resolved too, but it seems to be back, or still present, in todays (r15102m-071013) build.

 Platform : Archos Player
 Problem : + and - keys transposed when incrementing/decrementing settings, or scrolling through lists of setting choices - at the bottom level. There is no problem in the top levels, on the volume adjust key sequence, or in file browser, or virtual keyboard.
 
 I don't use the player much, so I don't know if this problem has only just popped up, but I seem to recall (90% sure) it was fixed last time.

« Last Edit: October 14, 2007, 03:56:56 AM by tspoon »
Logged

Offline ONE_HUMAN

  • Member
  • *
  • Posts: 22
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #206 on: November 06, 2007, 10:54:59 PM »
Quote from: jdgordon on March 31, 2007, 08:18:07 PM
fix committed

Too bad.  Preferred the way it was.  Would be nice if we could map the buttons ourselves, and I don't mean with a patch.
Logged

Offline AlexP

  • Member
  • *
  • Posts: 3688
  • ex-BigBambi
Re: BUTTON CHANGES - REPORT PROBLEMS HERE
« Reply #207 on: November 07, 2007, 03:28:40 AM »
This is nothing to do with the change in Sansa keymap.  It was 7 months ago and regarded to an internal change in how Rockbox handled buttons.

Will you please read threads before replying and stop spamming unrelated threads with your dislike of the button change.
Logged
H140, F60, S120, e260, c240, Clip, Fuze v2, Connect, MP170, Meizu M3, Nano 1G, Android

  • Print
Pages: 1 ... 12 13 [14]
« previous next »
+  Rockbox Technical Forums
|-+  Rockbox General
| |-+  Announcements
| | |-+  BUTTON CHANGES - REPORT PROBLEMS HERE
 

  • SMF 2.0.19 | SMF © 2021, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.186 seconds with 21 queries.