Hey, I recently updated to 1.0.3 and Unity 6000.0.23f1 and I can’t update my nodes’ properties anymore. Once I blur it, previous values appear.
Updating values directly on the graph works. (only inspector affected?)
1.0.2 shows the same behavior.
I tried using build-in nodes, creating new graphs, restarting the editor.
Please, let me know if I could provide more information about it.
Hi @mishakozlov74,
Can you please confirm if that issue happens if you press enter before blurring it?
We’ve had an issue with using non-delayed field updates which we need to work through, but if you press enter to confirm the value change I believe it should remain.
Hey, yes, apparently pressing Enter commits the changes!
But… Is there a way to have the previous behavior back? It’s a bit counter-intuitive to press Enter every time…
I’m actually surprised you say it used to work! I’m pretty sure it’s been a known issue for us for a long time. Are you sure it worked?
We definitely want to fix this, we need to resolve some things with the serialization for it to work properly and not cause the UI to lose focus 
Well, I remember tweaking those settings a lot and pressing Enter doesn’t seem familiar for me, so I guess it worked previously without it… Mystery!
I am surprised that the UI library (AppUI?) doesn’t support it out of the box, it seems to be working all across the Editor without pressing Enter?..
Whoops, I thought I responded to this! Sorry, I was actually on vacation the past few weeks so must’ve missed it and I’m catching up now 
The problem isn’t exactly with AppUI, to an extent.
UI Toolkit and AppUI have the option to either be delayed field, or an immediate changing field. If you set it to a delayed field (at least in AppUI), then de-focusing seems to cancel the edit instead of applying it.
But we explicitly use a non-delayed field, our system triggers serialization and the UI field refreshes which causes re-focusing issues while editing. We need to fix that on our side, and perhaps check with AppUI about de-focusing cancelling the edit.
Cool, take your time, I’m sure there are more important things to be done but nice that you have it in backlog!
Hi @mishakozlov74 , this is now fixed for 1.0.4
Is it correct that it hasn’t been released yet?
Correct! I’m hoping 1.0.4 will be out this Wednesday