if you find something working bad for this asset, just submit an issue

FastText 2.0 for Godot Engine

Fast text class for Godot Engine. It is a workaround for FPS drop on android devices when using Label and LineEdit nodes.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT."

NO WARRANTY, USE AT YOUR OWN RISK!

Godot (3.1 and 3.2) text rendering is not performing well on android devices: godotengine/godot#19917 FPS rapidly decrease from 60 to 45 just using 3 standard labels, that's no good. I made this custom class to keep performances in line.

You can use it as Label setting Allow Input to false You can use it as LineEdit (kind of) setting Allow Input to true

Allowing input means that an Input Box will appear runtime to allow text to be manually typed and saved in FastText node. Since it was developed with mobile devices in mind, standard Input Box will appear at the top of the screen (coord: 0,0) with full screen length. If you don't want this to happen, you can set custom position and size. As default, newly runtime-created Input Box will be put in Scene Tree as sibiling, but sometimes it is just not good: you can set a different location by using Input Box Parent. If you don't like standard input box, you can have one of your own nodes by using Input Node.

Class custom properties (1.0)

Property	domain	mandatory	desc
Fast Text	bool	no	activate Fast Text capabilities. Set to false to use as basic label node
Allow Input	bool	no	activate to use this node in a LineEdit kind of way
Target Type	control/sprite	yes	target rendered object. Default is control, but you can change as you please, if needed. Not considered when Allow Input is true
Shared Input Box	bool	no	for performances maniacs! If your project has a lot of FastText nodes that allow input, you could be bothered by the fact that each FastText creates a new input box by its own. Setting this option to true you can have any FastText node to create the ONE input box on first activation, and other FastText nodes will use that ONE instead of spawning new elements. NOTE: only nodes with this option enabled are going to use the shared input box.

When Allow Input is true, following properties are considered:

Property	domain	mandatory	desc
Input Node	NodePath	no	you can specify a TextEdit node you already put in Scene Tree you want to use instead of default input box. NOTE: remember that input node works in sinergy with FastText main nodes, it means you have to create a script who rightly behaves: for instance, just clone or extend already provided default script mentioned at Input Box Script property.
Input Box Parent	NodePath	no	you can specify a node in Scene Tree where you want put the default input box as a child. **
			NOTE : Input Node and Input Box Parent are mutually exclusive. If you leave them empty, Input Box will be created as a sibiling
Input Box Script	File Path	yes	mandatory when Allow Input is true. You don't have to code your own script, a default script has been already provided. If custom script is really needed, just clone default one and add your own code.

When Input Node is blank, custom Input Box will be created using following properties:

Property	domain	mandatory	desc
Input Box Style Inherited	bool	no	Input Box Style will be the same of TextEdit node
Input Box Style	StyleBox	no	Custom Style for Input Box
Input Box Font Inherited	bool	no	Input Box Font will be the same of TextEdit node
Input Box Font	Font	no	Custom Font for Input Box
Input Box Full Width	bool	no	when set to true, override width for Input Box will to screen full width
Input Box Custom Rect	Rect2	no	position and size for default Input Box

Class custom properties (2.0)

Coming soon

Install

Download Example to give a look.

Download FastText class 2.0 Unzip file to your project folder, then open Godot editor and add a new node "FastEdit" as you do when you add basic nodes.

NOTE: You can see two new classes: FastTextInit and *FastText". Even if both can be used with no differences, I suggest you use FastText one, it is simple and helps not to mess with custom class code :) .