Shaderblocks Dev 11: Introducing Uniforms

First of all, I'm really sorry for not updating Shaderblocks in the past three months. Due to this inconsistent update schedule, we are no longer naming our updates as Biweekly updates. Instead, we'll call them Dev updates, at least before v0.1.

Now for the changelog, this update includes:

• Uniforms
• Extended backward compatibility
• Various fixes and improvements on vector popup and autocompletion
• Fix error when all vector components are the same variable
• Fix expressions not updating after a variable is renamed or deleted

Introducing Uniforms
Uniforms are shader parameters that can be passed from CPU to the shader. With this, you can send data from script (e.g. GDScript) to your shader. For example, you have a dissolve shader, and you want to animate the dissolve amount, to do this you'll need a uniform called "Amount" and animate this parameter via AnimationPlayer.

Since textures are now uniforms, you can reuse the same texture in different blocks.

Extended backward compatibility
In the previous update, we have revamped the SBL format. Because of this, the newer Shaderblocks version is not compatible with older SBL files. It could convert and read the old format, but it was for SBL version BW9 only.
Now the converter can convert the older versions too, so you can now open your old files without resaving them in Shaderblocks Biweekly 9.

Better vector popup and autocompletion positioning
The position of vector popup and autocompletion is now clamped so it won't go outside the screen anymore.

The component menu will be moved to left when there's no space on the right

Bug fix: Autocompletion size not shrinking
Fixed a bug when a variable is deleted, the size of autocompletion will stay the same as before that variable is gone.

Bug fix: Autocompletion focus error
Fixed an error when you focus/hover on a variable on autocompletion then you delete that variable, and when you press up or down arrow you will run into the error

Bug fix: Error when all vector components are the same
Fixed an error when respective RGBA channels are like {var.r, var.b, var.g, var.a} then you get the error on gradient editor and Math Op (where the type of A is greater than B)

Bug fix: Expressions not updating when a variable is renamed or deleted
When a param expression contains a variable and then you rename or delete that variable, it should update the expression