Here is a first-pass attempt:
And here is the patch that you can have a play with.
After testing it out a bit, it seems it might be too temporary to notice when actually animating and focussing on the core content in the center of the view (as seen in the videos). I had originally thought that it would only really be necessary to show this during transform time, since this is when most transforms are likely to happen. So, if you were in fact making a series of edits, after it while you might start noticing the flashing and/or be able take corrective actions if necessary. However, on second though, this may still cause some unexpected keys to be set if using the clear transform tools, or other posing tools which don't have a modal loop.
Therefore, it might be necessary to keep a warning text in the corner where it now appears in this mockup under standard conditions, though without the border or icon, and probably not in red (no error here?). Something like:
Thoughts?
i think i saw something similar in lightwave (can be very wrong. saw it somewhere at least). they simply put the red border permanently around the viewport. i thought that was a pretty neat thing missing. Couldn't this flashing of the border be a little bit distracting?
ReplyDeletethe auto keying button should be more prominent to see that it is enabled. the notification in the corner during keying is nice but the flashing border is to much and would stop me doing my work.
ReplyDeleteI like the outline around the view. However it is not supposed to distract you but rather should be a warning. Therefore I would make it subtle yet noticeable which means: No unnecessary ornamental dashed line but a solid one. And given the red color, 1px would be sufficient.
ReplyDeleteLike the idea, think that the flashing could be distracting, maybe just a solid red as you transform?
ReplyDeletelooks useful but a themeable red frame is ok too, one thing that I enjoyed when implemented in other soft is a different color on sliders when a value is changed on a keyframe but no yet recorded... Blender already reads 'replace keyframe' so it is not that far, I wonder if it is feasible
ReplyDeleteI agree with SeriousM.
ReplyDeleteJiriH
I think it's very cool to have a reminder, it's so tedious to forget about having the autokeying when is not wanted. How can I test the patch, do I have to build blender myself?
ReplyDeleteOne thing that I'd add is the possibility to have the autokey button in the dopesheet, and not only in the timeline. I always use the dopesheet, and I used some scripts to put the autokeying in the N panel, but it takes space from the actual screen, and it's not ideal.
Regards, sebastian