It should be the same value as window.document.addEventListener("keydown", evt => console.log(evt.key))
Okay I find it, obviously It wasn’t LeftArrow like css but ArrowLeft
Love programming 
by user 224464722878005248
haha
Hi
I dropped my discovers here
First : If you want to had signed numbers with typescript you need to write
x : Number = -1;
and not x : number = -1;
Otherwise your x going to turn into a 0. (Typescript Novice mistake)
Secondly : There is some initialisations updates problems with needle
If you change a function it takes in count to update your project by unity
But when I tried to change number => Number in initialisation
The update doesn’t operate, so be carefull about it
I don’t know if it’s only because the compilator doesn’t see the differences between maj and minus letter or because it was out of an live circle function
by user 224464722878005248
So
To force recompile, try to save directly in your unity project
It’s going to take in count the number to Number change
by user 224464722878005248
Update : adding animation and change the default Layer doesn’t update either
by user 224464722878005248
What do you mean by that?
I also don’t quite understand what you wrote about the Number above? 
For example
If you write :
x : number = -3;
Before your start()
When you will use your x in your prog it’s gonna be 0
So it’s a problem
You change it in
x : Number = -3;
Yeah, normally it works, you will obtain -3
But after saving your Typescript file
It’s always 0
Why ?
Because you need to resave directly in your unity project
Like move an object, save, return the object in his original position and resave
And it will works
Otherwise the update of
x : number = -3;
To
x : Number = -3;
Don’t operate
by user 224464722878005248
And for animation, in the animation panel on unity
If you change anything in this panel and save
No update will operate too on your navigator
You need to replay the export
by user 224464722878005248
Ah I get it now.
I think the reason is that component gen generates a field for your public field x. So you have your component in Unity and it has a value of 0 set. So it doesnt matter if you change it in typescript because you serialize “0” from Unity. If you want to set the field from typescript and dont want a field in Unity you can annotate your field with @nonSerialized
E.g.
//@nonSerialized
x : number = -3
Yes - currently we dont trigger an export on asset saves automatically. This will be improved in the future but for now you have to save the scene or explicitly click “Export”
Oooh good to knew
by user 224464722878005248
Ok thanks
And
Just for now
I share you what I developed today for now
by user 224464722878005248
by user 224464722878005248
For more documentation about the component compiler and its annotations you can look here too
Awesome! Good progress
Do that
Only in one day, without knowing the framework
Your tool is very powerful
by user 224464722878005248
Yeah happy to see
Hi,
Just to notice :
I have often this error when I just save my project (after it I need to re-start the server)
by user 224464722878005248
Hey which exporter version are you on? when you get this error could you open the chrome console (F12) and screenshot the whole error for me?