...where you say to Louigi "Anyway, in what situations exactly do you want to let it save changes automagically without asking any questions? maybe that can be arranged ;)"
Would it be a bore to substitute the Enter/Return key for your 'save' dialogue, when this editor has the focus? That is: ENTER saves the edits, ESCape 'closes without saving' ?
BTW Rui, I disagree totally with your modest comment about QTractor being a toddler in the DAW field - as a longterm semi-professional user of certain German mainstream offerings, your sense of ergonomics coupled with the coding abilities to make it happen already put QTractor well within the 'commercial credibility league'. If you can maintain this clean smoothness and (apparent!) simplicity of use through all the upcoming increased complexity, you will end up with a DAW in a league of its own, IMO.
Obligatory caveat time:- Would it involve brain-busting 'codery' to somehow include any loop boundaries in the playhead's travels? That is, when using the back & forward (not the FF & Rewind) buttons, the playhead cursor stops at the loop boundaries as well as the edit boundaries? There again, perhaps I've missed something obvious... That's what comes of learning an app on-the-fly, I guess! ;-)
...where you say to Louigi "Anyway, in what situations exactly do you want to let it save changes automagically without asking any questions? maybe that can be arranged ;)"
Would it be a bore to substitute the Enter/Return key for your 'save' dialogue, when this editor has the focus? That is: ENTER saves the edits, ESCape 'closes without saving' ?
BTW Rui, I disagree totally with your modest comment about QTractor being a toddler in the DAW field - as a longterm semi-professional user of certain German mainstream offerings, your sense of ergonomics coupled with the coding abilities to make it happen already put QTractor well within the 'commercial credibility league'. If you can maintain this clean smoothness and (apparent!) simplicity of use through all the upcoming increased complexity, you will end up with a DAW in a league of its own, IMO.
Obligatory caveat time:- Would it involve brain-busting 'codery' to somehow include any loop boundaries in the playhead's travels? That is, when using the back & forward (not the FF & Rewind) buttons, the playhead cursor stops at the loop boundaries as well as the edit boundaries? There again, perhaps I've missed something obvious... That's what comes of learning an app on-the-fly, I guess! ;-)