Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://www.scirra.com/manual/180/progress-bar
"Form controls are actual HTML elements floating above the game canvas in the HTML page. Therefore, nothing can be displayed on top of a form control, apart from other form controls."
It also says form controls don't work well with scrolling. That could be a design challenge.
Thanks, @Fishou.
As for scrolling and form controls, you should avoid it whenever you can, it'll be janky (having a form control on a layer that doesn't move (like an HUD layer with a parrallax value of (0, 0)) works, as the form control won't move).
To be fair I try to avoid form controls in C2 games, except for a static menu for exemple, buttons in most cases can be replaced with sprites, progress bars with tiled backgrounds, Filechooser can have a 0 opacity with CSS and with a sprite under it while still being useable, and so on.
Textbox input is the trickiest one however, that's why I say to use it in static menus only.
the Text object (not textbox) however is not a form control (you probably know it but if someone else comes across this topic).