Up until now, several keys were assigned the same key value because the `keycode_lookup_table` array wasn't properly initialized. The values at the end of the array were all set to `KeyCode_Ex0 + 1` which is 112. This would cause several key to be treated as the same key. In my case the key next to the left shift key ( `<` and `>` on AZERTY) was getting the same value as the `Right Windows key`. But I suppose that the left and right windows key would get the same value too (I can't check this as I have only 1 windows key on my keyboard). This fix just properly initialize the array. I also fixed a typo in a function name: `keycode_physical_translaion_is_wrong` => `keycode_physical_translation_is_wrong`. |
||
---|---|---|
build_new | ||
code | ||
non-source | ||
triage | ||
.gitignore | ||
4ed.rdbg | ||
README.md | ||
TODO.md | ||
project.4coder |
README.md
4Coder Community
Welcome to the 4coder community repository.
Building
Windows
- Setup the MSVC toolchain in your environment, this can be done with the
code/custom/bin/setup_cl_x64.bat
script - call the
package.bat
script from the code directory$ cd 4cc\code
.\bin\package.bat
- You can also use the
build.bat
script if you want just build the binaries, this does not copy the default config, fonts and bindings$ cd 4cc\code
$ .\bin\build.bat
Linux
tested on Ubuntu 22.04:
-
Get required libraries (apt names):
$ sudo apt install build-essential libx11-dev libxfixes-dev libglx-dev mesa-common-dev libasound2-dev libfreetype-dev libfontconfig-dev
-
Use the
package-linux.sh
script to build and package an application$ cd 4cc/code
$ ./bin/package-linux.sh
-
You can also use the
build-linux.sh
script if you want just build the binaries, this does not copy the default config, fonts and bindings$ cd 4cc/code
$ ./bin/build-linux.sh
Mac (Untested)
- The steps should be the same as linux but replace the
*-linux.sh
with their*-mac.sh
equivalents.