3DS Development Unit GUI: Difference between revisions

(7 intermediate revisions by 3 users not shown)

Line 1:

[[File:dev_3ds.jpg|250px|thumb|left|Developer 3ds]]

A Developer (or Test) 3DS has two GUIs which can be used as a primary interface. Description of ~~these two interfaces are~~ taken from observations of a PAL 3DS Development Unit with Firmware 0.15.8 (revision 37901)

A Developer (or Test) 3DS has two GUIs which can be used as a primary interface. Description of homemenu interface was taken from observations of a PAL 3DS Development Unit with Firmware 0.15.8 (revision 37901). Description of testmenu was taken from testmenu v0.24.3 (revision 60260) cia.

== Home Menu ==

Line 19:

The Test Menu is a menu alternative to the Home Menu and has minimal functionality. It can be enabled by changing the 'Menu' option under "Other Setting" in the Config Menu to 'Test Menu', or by using the CTR Menu Selector (this is also a Developer App). Apart from its appearance, it has a number of restrictions that do not apply to the actual HOME Menu. Application region-checking is not performed by the Test Menu.

[[File:dev_testmenu_screenshot.png|250px|thumb|right|Test Menu for firmware 0.24.3 (r60260)]]

[[File:dev_testmenu.jpg|250px|thumb|right|Test Menu for firmware 0.15.8 (r37901)]]

Line 29:

Line 30:

* User name

* Remaining battery life

* Screen capture statut (Maybe for ctr debuggers?)

And on the lower screen:

* Test Menu status

* Explanation of Test Menu functions

The Test menu, can only launch Dev menu and slot 1 ~~devices~~. When the HOME Button is pressed while an application is running, that application is suspended and this menu is displayed;

The Test menu, can only launch Dev menu (,system settings on newer versions) and slot 1 device. When the HOME Button is pressed while an application is running, that application is suspended and this menu is displayed;

however, to return to the Test Menu, the application must handle a press of the HOME Button.

Note this is not possible where the developer has intentionally disabled the functionality of the home button, like in trade show sample~~. A video of someone using a dev unit with such a game can be seen here at [http://www.youtube.com/watch?v=B1iYD70oUxE]~~.

Note this is not possible where the developer has intentionally disabled the functionality of the home button, like in trade show sample.

When an application is suspended, pressing the L button takes a screenshot of the upper and lower screens, storing it into the Capture folder of the SD Card. This function won't work ~~have~~ if no SD Card is inserted.

When an application is suspended, pressing the L button takes a screenshot of the upper and lower screens, storing it into the Capture folder of the SD Card. This function won't work if no SD Card is inserted.

Files are generated in the following manner: [YYYYMMDD_HHMM date format]_[Screen]_[Index].bmp.

[Screen]: UL = upper screen, left eye image; UR = upper screen, right eye image; LO = lower screen

@@ Line 1: / Line 1: @@
 [[File:dev_3ds.jpg|250px|thumb|left|Developer 3ds]]
-A Developer (or Test) 3DS has two GUIs which can be used as a primary interface. Description of these two interfaces are taken from observations of a PAL 3DS Development Unit with Firmware 0.15.8 (revision 37901)
+A Developer (or Test) 3DS has two GUIs which can be used as a primary interface. Description of homemenu interface was taken from observations of a PAL 3DS Development Unit with Firmware 0.15.8 (revision 37901). Description of testmenu was taken from testmenu v0.24.3 (revision 60260) cia.
 == Home Menu ==
@@ Line 19: / Line 19: @@
 The Test Menu is a menu alternative to the Home Menu and has minimal functionality. It can be enabled by changing the 'Menu' option under "Other Setting" in the Config Menu to 'Test Menu', or by using the CTR Menu Selector (this is also a Developer App). Apart from its appearance, it has a number of restrictions that do not apply to the actual HOME Menu. Application region-checking is not performed by the Test Menu.
+[[File:dev_testmenu_screenshot.png|250px|thumb|right|Test Menu for firmware 0.24.3 (r60260)]]
 [[File:dev_testmenu.jpg|250px|thumb|right|Test Menu for firmware 0.15.8 (r37901)]]
@@ Line 29: / Line 30: @@
 * User name
 * Remaining battery life
+* Screen capture statut (Maybe for ctr debuggers?)
 And on the lower screen:
 * Test Menu status
 * Explanation of Test Menu functions
-The Test menu, can only launch Dev menu and slot 1 devices. When the HOME Button is pressed while an application is running, that application is suspended and this menu is displayed;
+The Test menu, can only launch Dev menu (,system settings on newer versions) and slot 1 device. When the HOME Button is pressed while an application is running, that application is suspended and this menu is displayed;
 however, to return to the Test Menu, the application must handle a press of the HOME Button.
-Note this is not possible where the developer has intentionally disabled the functionality of the home button, like in trade show sample. A video of someone using a dev unit with such a game can be seen here at [http://www.youtube.com/watch?v=B1iYD70oUxE].
+Note this is not possible where the developer has intentionally disabled the functionality of the home button, like in trade show sample.
-When an application is suspended, pressing the L button takes a screenshot of the upper and lower screens, storing it into the Capture folder of the SD Card. This function won't work have if no SD Card is inserted.
+When an application is suspended, pressing the L button takes a screenshot of the upper and lower screens, storing it into the Capture folder of the SD Card. This function won't work if no SD Card is inserted.
 Files are generated in the following manner: [YYYYMMDD_HHMM date format]_[Screen]_[Index].bmp.
 [Screen]: UL = upper screen, left eye image; UR = upper screen, right eye image; LO = lower screen