Inclusion of Screen-cast Key Status Functionality #76666

Closed
opened 2020-05-12 05:37:31 +02:00 by Campbell Barton · 13 comments

Adding this task as there has been an add-on developed for this,
while it needs changes to be acceptable, this task calls into question the use in having this functionality in Blender at all.

Adding this functionality either requires newly developed API's to hook into event handling, or to be built into Blender it's self,

Creating this task to check if this is functionality that would be accepted.

Pros

  • Everyone can access the functionality as part of Blender.

Cons

  • More code to update & maintain.
  • Having to maintain a key-overlay on top of everything else may cause issues or fail in some cases.
  • Tutorials using this wont work well if they involve any applications besides Blender.

See: blender/blender-addons#51419 (Screencast Keys Addon: Return to Addons release 2.79), blender/blender-addons#76611 (Screencast Key Status Add-on)

Adding this task as there has been an add-on developed for this, while it needs changes to be acceptable, this task calls into question the use in having this functionality in Blender at all. Adding this functionality either requires newly developed API's to hook into event handling, or to be built into Blender it's self, Creating this task to check if this is functionality that would be accepted. ### Pros - Everyone can access the functionality as part of Blender. ### Cons - More code to update & maintain. - Having to maintain a key-overlay on top of everything else may cause issues or fail in some cases. - Tutorials using this wont work well if they involve any applications besides Blender. ---- See: blender/blender-addons#51419 (Screencast Keys Addon: Return to Addons release 2.79), blender/blender-addons#76611 (Screencast Key Status Add-on)
Author
Owner

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Owner

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

IMO this is fine as an addon. The addon adds a panel in the Sidebar which we wouldn’t want by default, and really this sort of thing isn’t core to creating 3D content. Other apps typically don’t include this kind of thing, and external apps exist for screen recording which both record and display keys across all applications used.

IMO this is fine as an addon. The addon adds a panel in the Sidebar which we wouldn’t want by default, and really this sort of thing isn’t core to creating 3D content. Other apps typically don’t include this kind of thing, and external apps exist for screen recording which both record and display keys across all applications used.
Author
Owner

If it was only a matter of having the add-on as an optional component, that could be OK (assuming bugs references from blender/blender-addons#51419 are resolved).

The issue is there is extra development involved to support this, which raises the question if this is worth spending time on.

If it was only a matter of having the add-on as an optional component, that could be OK (assuming bugs references from blender/blender-addons#51419 are resolved). The issue is there is extra development involved to support this, which raises the question if this is worth spending time on.
Member

Added subscriber: @nutti

Added subscriber: @nutti
Member

I think adding API would be better than adding Screencast Keys to Blender itself.
Screencast Keys add-on targets to the user who make tutorials, which is not essential to create contents as mentioned before.
Switching between enable and disable is one of the benefit for add-on.
Furthermore, there will be spaces to tweak an UI if this feature is left as add-on for some advance users.

I think adding API would be better than adding Screencast Keys to Blender itself. Screencast Keys add-on targets to the user who make tutorials, which is not essential to create contents as mentioned before. Switching between enable and disable is one of the benefit for add-on. Furthermore, there will be spaces to tweak an UI if this feature is left as add-on for some advance users.

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
William Reynish self-assigned this 2020-05-12 10:21:06 +02:00

After discussion, we are closing this topic. While useful for some folks, we don't think it's worth the time to include this in Blender's core. It's outside the main scope of what Blender's core feature set should be focused on.

After discussion, we are closing this topic. While useful for some folks, we don't think it's worth the time to include this in Blender's core. It's outside the main scope of what Blender's core feature set should be focused on.
Member

Understood. Thanks for sparing time for this.

Understood. Thanks for sparing time for this.
Author
Owner

@nutti, to be clear, we're not against this in principle, however supporting this involves writing new API's.

If someone is interested to do this, it could be included in Blender. However the API should not introduce too much complexity & maintenance-overhead into existing code.

@nutti, to be clear, we're not against this in principle, however supporting this involves writing new API's. If someone is interested to do this, it could be included in Blender. However the API should not introduce too much complexity & maintenance-overhead into existing code.
Member

Thanks for your follow up comments.
Yes, I understood the range of development for this function and the directions.
For now, I think it may be better to continue hosting this function as the external add-on in my repository.

BTW, writing & contribution of new APIs by non-committer are welcomed?
I do not know well the process of development about Blender's C code.

Thanks for your follow up comments. Yes, I understood the range of development for this function and the directions. For now, I think it may be better to continue hosting this function as the external add-on in my repository. BTW, writing & contribution of new APIs by non-committer are welcomed? I do not know well the process of development about Blender's C code.
Author
Owner

New API's by non-committers is fine.

New API's by non-committers is fine.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#76666
No description provided.