Screencast Key Status Add-on #76611
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#76611
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Screencast Keys add-on is an add-on which displays the key & mouse event.
I think many people know about this add-on and removed from official repository due to lots of issues as mentioned below.
https://developer.blender.org/T51419
I have worked on this add-on since Blender 2.8 was released.
https://github.com/nutti/Screencast-Keys
In the process to port this add-on to Blender 2.8, I rewrote whole of codes and fixed the bugs mentioned there.
Also, lots of people used & tested this add-on, which makes this add-on improved in functionality and user interface.
https://github.com/nutti/Screencast-Keys/issues?q=is%3Aissue+is%3Aclosed
Many people still uses add-on to make tutorial, but some people confusing about the versions which they should use because of removal of this add-on in past.
Therefore, I think it is a good idea to return to official repository to provide the newest & bug fixed version.
I will maintain this add-on in the future, so the lack of maintainer will not be matter.
What do you think about this idea?
Thanks!
Added subscriber: @nutti
Added subscriber: @ankitm
Hi!
Have you seen https://wiki.blender.org/wiki/Process/Addons ?
@ankitm
Sure.
Before moving on code review, I would like to discuss the plan about Screencast Keys add-on itself.
Or, is it possible to create diffs directly?
If yes, I will cleanup the add-on's code and make code review request.
Thanks for your concern!
hi @nutti, I have no problem with this being added back. I've been following your progress for some time now.
Given the importance of this addon and it's worth looking at.
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @ideasman42
@ideasman42 hi, I would like to target this for 2.84 bcon1. @nutti has maintained and fixed this addon over many releases and solved the issues that caused it's initial removal.
Thanks.
Personally, I'd rather not support this. As long as it's constrained to a single area this gives less useful results than equivalent tools that run on the operating system.
Besides this, the add-on depends on referencing Blender's internal event handlers which is fragile and will break as we make changes to Blender it's self.
https://github.com/nutti/Screencast-Keys/tree/master/src/screencast_keys/utils/c_structures
This needs to be removed if the add-on is considered for inclusion with Blender.
If this is supported, it could be written as part of Blender as run at the window level, not per area. Either the Python API would need to support this without hacking into our C structures, or it could be written as part of Blender without using the Python API.
Thanks for your comments.
I think this limitation can be came over by using 'Set Origin' operation and 'origin' option in this add-on.
Also, there is an option which runs at window level.
I agree with this.
However, I could not query events only in current Python APIs.
Is there any possibility to add Python APIs which queries all events in queues on wmWindow struct in future?
If so, I could implement this add-on without any hackings to C structures.
Adding API calls is possible, although the API calls are likely to be so spesific to this add-on that we might just as well add the feature to Blender it's self.
If we have to maintain special API's for this feature in Blender, this brings us back to the question of this functionality being something worth investing development time in.
Closing this task since this is more a design topic (including screen-cast key status functionality).
Added design task for this blender/blender#76666 (Inclusion of Screen-cast Key Status Functionality)
Changed status from 'Confirmed' to: 'Archived'
I left some comments on new task.
Thanks for considering this topic!