Search Issue Tracker

Fixed

Fixed in 6000.4.1f1, 6000.5.0b1, 6000.6.0a1

Votes

0

Found in

6000.4.0b7

6000.5.0a6

6000.6.0a1

Issue ID

UUM-133613

Regression

No

Every number entered in the Graph Toolkit's numeric field is considered a separate change

Graph Toolkit

-

How to reproduce:
1. Create a new Unity project and import the "MySimpleGraph" Script
2. In the Project window, right-click -> Create -> Graph Toolkit Samples -> Simple Graph -> Open the Graph
3. In the Blackboard, create a new Float variable and expand it
4. Enter "123" into the field
5. Press "Ctrl + Z"/"Command + Z" and observe the results

Expected results: The value in the field is 0
Actual results: The value in the field is 12

Reproducible with: 6000.4.0b7, 6000.5.0a6

Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested

Note: This is inconsistent with all numeric and string fields in the Editor, as well as with string fields in the Graph Toolkit

  1. Resolution Note:

    Default Value fields in the blackboard have been updated so they use the delayed modifier. This means that they will only update their property value when either the user presses Enter or the text field loses focus.

    This change was also made for the fields in Constant Nodes and Subgraph Nodes, since these fields cannot be created using the public API and should use the default delayed setting.

  2. Resolution Note (fix version 6000.6.0a1):

    Fixed in 6000.6.0a1

  3. Resolution Note (fix version 6000.6.0a1):

    Default Value fields in the blackboard have been updated so they use the delayed modifier. This means that they will only update their property value when either the user presses Enter or the text field loses focus.

    This change was also made for the fields in Constant Nodes and Subgraph Nodes, since these fields cannot be created using the public API and should use the default delayed setting.

  4. Resolution Note (fix version 6000.5.0b1):

    Fixed in 6000.5.0b1

  5. Resolution Note (fix version 6000.4.1f1):

    Fixed in 6000.4.1f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.