This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#9869 - For a setting screen, if the cursor does not move, the selected item's value is invalid.
Attached to Project:
Rockbox
Opened by Yoshihisa Uchida (Uchida) - Tuesday, 03 February 2009, 11:29 GMT+2
Last edited by Jonathan Gordon (jdgordon) - Friday, 18 December 2009, 07:41 GMT+2
Opened by Yoshihisa Uchida (Uchida) - Tuesday, 03 February 2009, 11:29 GMT+2
Last edited by Jonathan Gordon (jdgordon) - Friday, 18 December 2009, 07:41 GMT+2
|
DetailsFor the setting screen, I do not move the cursor and I select the current item.
Then, when option_screen() returns, *(int*)setting->setting does not set the current item's value. If the cursor moves, and the top item selects, then *(int*)setting->setting sets the current item's value. I send this bug's patch file. An sample program was prepared. test_sample.c copies apps/plugins and SOURCES edits. Then test.sample.rock builds and it runs from Rockbox. |
This task depends upon
Closed by Jonathan Gordon (jdgordon)
Friday, 18 December 2009, 07:41 GMT+2
Reason for closing: Not a Bug
Additional comments about closing: Yoshihisa, You need to fix that patch so you dont need to know if the setting was canceled, or do your own list handling.
Friday, 18 December 2009, 07:41 GMT+2
Reason for closing: Not a Bug
Additional comments about closing: Yoshihisa, You need to fix that patch so you dont need to know if the setting was canceled, or do your own list handling.
It is not understood whether the selection of the item had been canceled from the return value and arguments of set_option() (or option_screen()).
Therefore, different processing cannot be done whether for the item to have been selected.
Then, I thought whether be able to judge that the selection of the item was canceled if the value of "val" after set_option() was executed was an invalid value.
FS#9892, I made the patch that made it jump to the first page when the bookmark was not selected.I found this bug while making the above patch file.
Does something good method exist?