I have fixed the conflicts, however. Soon it will be available for merge request in paceholder

The UI is better, but the example is not yet very good.
Computation nodes (e.g., division, multiplication) should default to an empty icon.

I also do not understand the logic behind random generation. Sometimes it throws an error. Sometimes it doesn't.

The image shows a processing icon for a node that has empty input.
Nodes with empty input showing a valid icon
And a node with an error showing a valid icon.

We should have a very functional example before suggesting a PR.

Other examples are also displaying the processing status when they shouldn't.
As we talked, the default option should omit the processing status functionality. It should be optional for the developer to implement it or not.

Now, to address these example issues, the following changes were made:

1. No default value for the processing status in the Node Delegate Template, as the processing status icon issue that appeared in other examples was triggered by this default value.
2. Empty processing status appears until all inputs for the node are provided (in the example, the two numeric inputs for the Random Number Generator node).

And, to explain the appearance of the Error processing status, there is a conditional statement that change the control flow when the first input for the node (the top one) is greater than the second input (the bottom one), so that the Error processing status can also be displayed and seen as a processing status option by the PR reviewer. The conditional statement is as follows:

double a = n1->number();
double b = n2->number();
                
if (a > b) {
    SetNodeProcessingStatus(QtNodes::NodeProcessingStatus::Failed);

    emit requestNodeUpdate();
    return;
}

So, the goal is to keep a random number being generated in the range [a,b] ([n1, n2]), as described in the Random Number node class docstring. These control flow details will be explained in the final nodeeditor PR!