Start the emulator.
Also, depending on the setting, the connection function to the emulator is enabled at the same time, and information such as the event etc. is acquired from the emulator.

Start the emulator 2.
If no $ gba debugger is specified, the sav file of emulator 1 is transferred.
It also makes it easier to generate symbol files automatically for debugging.

After changing something, if you check with the emulator at F5, if you encounter problems that can not be solved by all means, it is assumed that you press Ctrl + F5 and debug the contents with no $ gba debugger.

Click the “Write To ROM” button in the item that is currently being changed.
For event script etc, click “Change” button.

Please change it and use it when it is troublesome to push the write button one by one.

Close the current window.
For pages opened in tab form such as event scripts, close the currently active tab.
Unlike Ctrl + F4, only the currently active tab is closed.

Go to the main window.
Since FEBuilderGBA opens several windows, please use it when you want to return to the main screen immediately.
It is like a home button on a smartphone.

Open the Binary Editor.

By the way, you can start the binary editor by double clicking on the selected address on each screen.
You can also make nmm modules, dump with csv, tsv, EA.

You can set key bindings and functions from the setting shortcuts.

Other functions are as follows.

It is a shortcut that does nothing.
It means that it is unset.

By default, it is assigned to F5.
Open the edited ROM with the emulator.
Probably the most used function.

By default, it is assigned to Ctrl + F5.
Open with the debugger emulator.

By default, it is assigned to F11.
Open the Binary Editor.

Open the last file you used.
For example, after saving an image, you can run that image in association or select it in Explorer.

Open the ROM you are currently editing with sappy.

Open the ROM you are currently editing with the program you specified

Open the screen to cancel the editing.
It seems to be important, but it is quite a shadowy function.

Display the log of FEBuilderGBA.
This is also a shadow thin function.
Aka Rin -

Go to the main window.
By default, it is assigned to Pause (Break).

Press the write button.
By default, it is assigned to Ctrl + K.

Close the window.
By default, it is assigned to Ctrl + W.

Activate FELint and check for errors that can be automatically detected in the ROM.
FELint can also be launched from the menu, and errors in chapters currently being edited are also displayed on the right side of the main window, so it is not clear whether or not there is a meaning to register shortcuts … well.

Open a new ROM.

Save the current edited contents in ROM.
However, if possible, we recommend using the function of “18”.

Save the current ROM as a different name.

Execute FELint on the ROM and save it if there is no error that can be detected automatically.
If there is an error, save is canceled and an error list is displayed.


In addition, if you have the shortcut you want, please post it to the community.

The available places are limited, and there are shortcuts that are decided.

Undo
Cancel the operation.

Redo
Cancel cancellation of operation. (Undo it)

Copy
Copies the selected contents to the clipboard.

Paste
Paste the contents from the clipboard.
When used in combination with Ctrl + C, you can increase the data.

It is effective only in the event editor system.
Instead of seeing the written event, I will change it directly.

Valid only with binary editor and 3 point DIFF.
Draws the mark at the position where the cursor is currently located.
Press again to release the mark.

Please use it so as not to get lost where you are.

Valid only with binary editor and 3 point DIFF.
The mark list is displayed.

Valid only with the binary editor.
Search with specified content.

Valid only with the binary editor.
Jump directly by specifying an address.

In the binary editor, it is the same as Ctrl + G.
Jump to the specified address.

In the case of the event editor system, it moves to the first item.
For example, if the first item is a unit it opens the unit screen, and if it is an event to be nested, we will move to that event.

It is effective only in the event editor system.
I will go directly to the second item.
For example, if the second item is a unit, we open the unit screen, and if it is an event to nest, we will move to that event.

It is effective only in the event editor system.
Delete the data at the cursor position.

Close the dialog.