There are cases of hard-coded keys to which there’s no alternative. Would you also suggest everyone to just use the ‘Blender’ one? That will never work. Practiced users will assign their own keys to things they use the most, and it’s up to them to figure out what they are. Keys are preference, and should be a preference. Instead of teaching what keys to mash, teacher should show what tools to use and where to find them. That add-on should whither and die (no offense to its makers, it may have served a purpose once, but that purpose is now long dead). But I think that these three simple things would go a LONG way toward lessening the reputation that blender had that it is hard to learn or has a steep learning curve A LOT of people are going to be quite upset with me. Ok I know some people are going to disagree with me. If you just use the standard “out of the box” blender version you will get less questions of the type “My screen does not look like that.” Just because you like a theme or screen setup does not mean everyone does. AND PLEASE NO DEV versions or special builds. The version without screen adjustments or themes or you favorite interface addons or colors. Use the standard Blender Foundation Latest Stable version of blender when you do your video tutorial.
#Blender screencast keys how to#
So we just ASSUME that everyone that uses Blender knows how to do those things. But those of us that know blender so well just do things automatically without thinking of it. The screencast keys mentioned above will show the viewer a lot so they will not get frustrated. Just because you know how to do something in blender does not mean that your viewer knows how to do it. It’s like they think the viewer can read their mind. This addon had been part of blender for years now and it still amazes me how many people post video tutorials and just naturally assume that the viewer can see what keys they are pressing or what mouse button they are clicking.
We could also look into solving other issues like with modal operators, either by extending the BPY API or by implementing this feature in C (similar to how pies are an Add-on with C implementation).These are three pieces of advice that I think are most important for a tutorial maker… Just as an aside I have been using blender for 18 years now.
I suggest for 2.8 we bring this feature back but move it into the (). * Every key typed in the text editor was displayed by the Add-on. * It didn't work with most modal operators. * It only worked for the 3D View, not for other editors. * To my knowledge there wasn't an active maintainer at that time, which is against our rules for keeping Add-ons in the list of officially supported Add-ons. That's too much of a back-and-forth to be reasonable. With that in mind, I'm definitely against bringing this back for the 2.79 release, just to eventually replace it with a different version solving some of its current issues in 2.8. We could also look into solving other issues like with modal operators, either by extending the BPY API or by implementing this feature in C (similar to how pies are an Add-on with C implementation). I suggest for 2.8 we bring this feature back but move it into the global status bar. So people kept reporting bugs but there was nobody maintaining the Add-on to fix them (see #37865, #36840, #40173, #37517. Every key typed in the text editor was displayed by the Add-on.It didn't work with most modal operators.It only worked for the 3D View, not for other editors.To my knowledge there wasn't an active maintainer at that time, which is against our rules for keeping Add-ons in the list of officially supported Add-ons.
The key-repeat issue was not the only reason for removing this Add-on:
0 kommentar(er)
