This comes up from time to time. The usual workaround is to create a preset with the default values if that's what you want.
The thing is, many parameters have relatively arbitrary defaults. I'm wondering what you would use this for?
Another thing is that I'm toying with the idea of allow user configurable defaults (loaded from a .amh file somewhere) which might not interact well with this suggestion.
If this were an easy change I'd do it straight away but the way things are at the moment, contraptions completely forget their default settings... so let me know what you'd use it for -- perhaps there's an even better solution which would take the same or less time for me to implement.
Reloading the whole patch would be troublesome if you only wanted to reset some key things that you tweaked in a bad way. It could also help in a live situation when you accidentally do something that sounds horrible you could quickly change it back to a meaningful setting.
>>>
It could also help in a live situation when you accidentally do something that sounds horrible you could quickly change it back to a meaningful setting.
<<<
Is this why you want the function?I have my doubts whether the default setting will be universally useful in this case.
One possibility is to provide Undo on parameter changes. I have intentionally avoided this up until now, but it would be a better option than reset to default I think, for the case you describe above.
Besides, in performance you have to learn to live with your mistakes ;-)
Not sure I was clear or not but by default I meant, if you open an .amh you made you can have a way to reset just one parameter to the way it was when you last saved/loaded. it could be good for when some tweaking gets out of hand but resetting the whole patch in order to quickly settle something bad would mean loosing something good. This would be mostly helpful for the more complicated/messy patches with lots going on.
It would go perfectly hand in hand with undo: you can reset a parameter to "default" then if that wasn't the parameter which was causing the problem you could just hit undo and so on.
This comes up from time to time. The usual workaround is to create a preset with the default values if that's what you want.
The thing is, many parameters have relatively arbitrary defaults. I'm wondering what you would use this for?
Another thing is that I'm toying with the idea of allow user configurable defaults (loaded from a .amh file somewhere) which might not interact well with this suggestion.
If this were an easy change I'd do it straight away but the way things are at the moment, contraptions completely forget their default settings... so let me know what you'd use it for -- perhaps there's an even better solution which would take the same or less time for me to implement.
Thanks
Ross
Reloading the whole patch would be troublesome if you only wanted to reset some key things that you tweaked in a bad way. It could also help in a live situation when you accidentally do something that sounds horrible you could quickly change it back to a meaningful setting.
>>>
It could also help in a live situation when you accidentally do something that sounds horrible you could quickly change it back to a meaningful setting.
<<<
Is this why you want the function?I have my doubts whether the default setting will be universally useful in this case.
One possibility is to provide Undo on parameter changes. I have intentionally avoided this up until now, but it would be a better option than reset to default I think, for the case you describe above.
Besides, in performance you have to learn to live with your mistakes ;-)
Ross.
Not sure I was clear or not but by default I meant, if you open an .amh you made you can have a way to reset just one parameter to the way it was when you last saved/loaded. it could be good for when some tweaking gets out of hand but resetting the whole patch in order to quickly settle something bad would mean loosing something good. This would be mostly helpful for the more complicated/messy patches with lots going on.
It would go perfectly hand in hand with undo: you can reset a parameter to "default" then if that wasn't the parameter which was causing the problem you could just hit undo and so on.