programnoir / gdtemplate Goto Github PK

Time to add fonts and font options to the project. The goal is not to offer a variety of font options for aesthetic themes, but to utilize fonts that are designed with intent of improving accessibility.

(English) Accessibility fonts:

• Atkinson Hyperlegible - General purpose, balances aesthetics and targets a wide variety of vision issues that people experience. Has its own permissive license that allows for incorporation into the project.
  • https://brailleinstitute.org/freefont
• Lexend - Variations designed to increase reading fluency and reduce errors with a clearer font face with spaced lettering. Measured in a classroom environment to improve fluency by roughly 20%.
  • https://www.lexend.com/
• OpenDyslexic - Specialized font, widely known and used in a variety of applications already.
  • https://opendyslexic.org/

Language fonts:

• Noto Sans - Covers over 1,000 languages, licensed with Open Font License.
  • https://fonts.google.com/noto
  • https://fonts.google.com/noto/specimen/Noto+Sans+JP
• LiS Font Walnut/LiS Font Cashew
  • Two dyslexia-friendly font families developed by researcher Xinru Zhu and colleagues at the University of Tokyo.
  • Edit: These fonts are not yet available to the public, but they're working on another font (https://www.jibun-font.com/).
• UD Digital Kyokashotai (https://www.typebank.co.jp/fontfamily/uddkyo/)
  • Universal-design font, with evidence-based improvement for those with dyslexia/amblyopia.
  • Appears to require a license before it can be used.
• BIZ UD Gothic (https://github.com/googlefonts/morisawa-biz-ud-gothic)
  • Recommended as a possible open-sourced alternative font.

Nice going, me. Thoroughly test the thing, next time.

There are black borders along the top and bottom of the screen. This may be related to how the content scaling of the project works specifically. It is most likely that the solution could involve changing the size of the window itself. I'll need to explore this in more detail to get this issue ironed out.

Add the option to enable borderless windows in settings > video tab.

Per the wiki's guidelines, the project will need an update the correctly renames folders, nodes, variables, and so on, until the style guidelines are properly adhered to.

This project needs both documentation and a code cleanup pass. For now the guidelines need to be defined.

Steps to replicate:

1. Open game
2. Navigate to video tab
3. Increase window size. On a 1920x1080 screen, this should max out at 4 (when it converts to fullscreen).
4. Press the button again, which makes no change to the window or fullscreen but increases the text label to 5.
5. Label is also able to reach 0.

• Tries to access a size property instead of calling the size() function.
• Improperly clamps the current keyframe to the size of the keyframes array instead of the size - 1.

Fixed in new branch, will merge soon.

Since GDTemplate is at a reasonably stable state, I'm going to move forward with porting a plugin featuring the dialog database as well as an example UI for it.

This occurred because I only have a 1080p monitor and failed to specify maximum font size values for monitors of that size.

Context for those seeing this: You can increase the scale of the UI content in this template, and this impacts the size of the font, which you can also change. To avoid text being too large for the UI, maximum font sizes need to be specified according to game scale. Because I have a 1080p monitor, my game scale only went up to 4, so I created an array for maximum font sizes for up to 4 values -- it's something that developers can easily modify (if they can find it, which is a separate issue), but the UI on the player's end can do weird stuff if these values are not set.

Probably should've considered a smarter solution than an array, haha. Probably the best course of action to handle this is to set up a mathematical fallback formula based on the current values for these fonts.

Steps to reproduce:

1. Open game
2. Select New Game.
3. Game will fade out
4. Debugger produces error message while fading in.

Message: E 0:13:51:0094 step: <Tween#-9223371888745510804>: started with no Tweeners.
<C++ Error> Method/function failed. Returning: false
<C++ Source> scene/animation/tween.cpp:301 @ step()

This is a first-time setup menu that attempts to accommodate users who are launching a game for the first time.

• This menu should be very simple - A more detailed settings menu comes right after.
• Language/Accessibility
  • Language and accessibility features should be offered first.
• Audio
  • Don't play music in the beginning.
  • Option to set premaster to 0%
  • Dedicated sound effect volume slider.
• Essential video features (window size/fullscreen and game scale).

Ideas for this menu that would need to be implemented separately:

• Narrated options.
• Dark or bright UI themes.
• Font selection
• Font size

Currently, the names of Actions and InputEvents cannot be translated, meaning that the keybinding section of the template is exclusively in English. The main idea to fix this would be to provide translations for the unhidden built-in actions as well as the InputEvents that can be assigned to them.

Need a simpler folder and file naming system than the one currently being used. Some laptops are running into particular issues with filepaths being too long.

Caused by an invalid variable name reference in the signals file of the float manager in the dialog database.

Issue is fixed in the current branch as it's needed for testing the dialog nodes but I may need a branch to resolve this bug while I work on the example dialog UI.

Once the database editor is merged, the next thing to do is create an example dialog system that demonstrates some of its features.

Every change I make to the editor is adding nonsense to my github commits. Only the changes to the actual project need to be considered.

Keyboard navigation allows for players to navigate between tabs, but if the text of tabs is too large, it only brings the focus into view enough that the button displays, while the next tab does not.

In this visual example, the Audio tab cannot be clicked because it is still cut off and fails to be accessible via mouse.