But you can also access "raw" text input using

app.textInput.start()

Using EditText:

haxe
var someText = new Text();
someText.color = Color.WHITE;
someText.content = 'someContent';

var selectionColor = Color.BLUE;
var textCursorColor = Color.WHITE;
var editText = new EditText(selectionColor, textCursorColor);
someText.component('editText', editText);

editText.onStart(this, function() {
    // Started editing text
});

editText.onUpdate(this, function(text:String) {
    trace('text updated: ' + text);
});

editText.onSubmit(this, function() {
    // Edited then pressed "enter" or similar
});

editText.onStop(this, function() {
    // Stopped editing text
});

what's the effective difference between them?

app.textInput.start()

is not providing the graphic part of the text input

If you just want to create an editable text field you should use the example abuve

oh i should ask here

i've been having this very annoying problem with sppine in ceramic

the slime is deformed for no reason

i've been trying to figure out what the problem is for the past four days

it looks fine in editor but it comes out like this in ceramic, like the top bone is off by about 30 degrees and some other stuff

even on a fresh new ceramic project

nevermind? maybe? version? ???

Seems like a bug in spine runtime. Which version of the editor are you using?

i fixed the issue, it had to do with versions and/or a bone's scale being set without me realizing

Render textures that support antialiasing (multisampling) is coming soon to Ceramic...

Up until now, antialiasing was only possible on content that is not rendered onto a render texture (rendered to screen directly)

so, after a moderate amount of experimentation, I believe I've found an issue with spine in ceramic

If the mix between two animations is shorter than the elapsed time between frames, the spine glitches out and stops moving

I'm using tracks, but only one track, so I haven't yet tested if it affects only that one track or the entire spine

Sounds like a problem very specific to spine. Could be a problem in the spine runtime for haxe, but could also be a bug from official runtime. Do you have any error logged when the glitch happen?

no error or warning or anything, it just stops

i tried to run it in the official skeleton viewer, which i hear uses the java/libgdx library (that spine-hx is converted from) but it is apparently just broken and doesn't even start up right

to help with testing, can i change the target framerate while the game is running?

Yes, you simply set settings.targetFps = your fps

im just past the square tutorial and i think im gonna cry because of how nice ceramic is

the api looks so easy to use

bless haxe and the amazing libraries that come with it 🙏

Hey, I'm always happy to get such feedback about Ceramic thanks 🙂

thought ill share, feeling proud of my highscore lol

thats a really nice game