I'm confused, i thought that's what you were looking for?!

You said "reset to initial values".

And that's exactly what it does.

First of all I appreciate you're trying to help :)

Sorry about my bad English, on my original thread I tried to explain what I'm trying to do:

I'm trying to have "RESET" button for each slider so it can bring back both Variable and Knob Values to the original / initial numbers that I insert on the Instance Variable "Value".

I wish I could describe it better.

That's cool! it seems like THERE IS some kind of a "system" in this Software Versioning.

I still find this minor thing very interesting, thanks for sharing!

gofile.io

I've set a default instance variable directly onto the knob.

Of course your could also set local variables directly into the code.

Or use global variables instead.

But this should work just fine.

Thanks for give it a try Everade I just had a quick look but it's just resetting the knobs.

I mean, it doesn't do what I'm trying to achieve which is reset to the Default (initial) values and also put the knobs on the correct position.

Are people really too lazy to manually change a 1.0 to a 1.1 now?

Not at all, the original thread is HOW it's done if there is a common known "system" that developers use to calculate the changes or rather just throwing numbers based on the size of the changes 0.001 / 0.1

That might be an interesting feature request, but how would it update?

By save, or export, etc.?

OH! I never thought about it as a feature but... maybe it could be? not sure how as well.

I think it should stay something that we do manually but for now I think people still doing this manually by updating their X-Sheet with each Bug-Fix / New-Feature and somehow... throw a number tiny, or big based on the measure of the change.

I don't think people really care about this much, but I found this very interesting for some reason. :)

In general you update the version when there is a new 'release'. Some minor bug fixes you increment by .X so 1.1 and major features you could think about updating the version number so 2.0.

Thanks plinkie, so it's similar to my example as I thought it's more like throwing numbers in a way :)

But it's good to know that I didn't miss some common or known system, I was curious about if there was anything organized like that or not.

Hey All,

Just to be clear I'm not talking about our Project Files which could be named anything on our backup Hard Drives...

I'm talking about the actual published Splash Screen or About > Version we usually see on any software and also available in C3's Project properties.

.

Since I'm new to developing I wonder about how it's done:

How do I "calculate" what number of version to update after every X changes?

Are there any common "rules" that are known between developers instead of just throwing numbers around?

For example:

For every X Bug Fixes + 0.001 to the current version number

For every X New Features + 0.1 to the current version number

etc..

I'm just curious if there is an actual known system of doing this correct or I just throw numbers which seems weird to me but may not be that important, it's pure curiosity but please feel free to share your knowledge. :)

AllanR, dop2000 and Ashley your tips are very helpful for sure, I take nothing for granted!

I appreciate your encouraging message Allan, it is true that as a non-programmer + LOTS OF HELP from the community I could actually bring a VERY useful toolset to life. I don't see how I could do anything close to it by myself without hiring someone do program it.

.

I'll just have to deal with what I have and hope that people won't go MAD when the size will become insane compare to what it's actually includes.

Ashley does have a point, steam users usually download so many things... I hope they don't mind because it's a bit different than grabbing a solo file and notice it's obvious size.

.

As I said I'm learning new things every day thanks to this amazing community :)

Thank you everyone!