studio
/
blender-studio-pipeline
10
24
Fork 17
Code Issues 6 Pull Requests 3 Projects Releases 1 Activity

Blender Kitsu: Add Frame Range Warning even if no Kitsu Context is Found #130

New Issue
Closed
opened 2023-07-19 16:27:51 +02:00 by Nick Alberelli · 0 comments
Nick Alberelli commented 2023-07-19 16:27:51 +02:00
Member
Copy Link

Original Request by @SimonThommes

Hey, the frame range thing is still a bit of an issue, right now, when you open 070_0010.lighting the context in the kitsu addon is not auto-detected. when I click the button to do that, it works fine, but the warning doesn't show. It only does after I save and reload.

Frame Range warning pop-up doesn't appear when the file context doesn't load.

TODO:

Find a way to filter for only files related to the current project, and show frame range warning on those files, excluding files unrelated to the current project.

Original Request by @SimonThommes > Hey, the frame range thing is still a bit of an issue, right now, when you open 070_0010.lighting the context in the kitsu addon is not auto-detected. when I click the button to do that, it works fine, but the warning doesn't show. It only does after I save and reload. Frame Range warning pop-up doesn't appear when the file context doesn't load. TODO: Find a way to filter for only files related to the current project, and show frame range warning on those files, excluding files unrelated to the current project.
Nick Alberelli added the
Kind
Enhancement
Kind
Studio Request
 labels 2023-07-19 16:27:51 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
New-SVN-features
julienkaspar-troubleshooting-feedback
julienkaspar-svn-feedback
julienkaspar-install-software-feedback
blender-studio-navbar-global-match
vertex-group-topology-transfer
mets-naming-conventions
latest
Labels
Clear labels   
Kind
Breaking
Breaking change that won't be backward compatible

  
Kind
Bug
Something is not working

  
Kind: Community

Issues opened by members of the community / outside the studio

  
Kind
Documentation
Documentation changes

  
Kind
Easy
Simple to complete

  
Kind
Enhancement
Improve existing functionality

  
Kind
Feature
New functionality

  
Kind
Proposal
A proposal or idea that requires feedback

  
Kind
Security
This is security issue

  
Kind
Studio Request
Requested by a user at the Blender-Studio

  
Kind
Testing
Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
Kind
Breaking
Kind
Bug
Kind: Community
Kind
Documentation
Kind
Easy
Kind
Enhancement
Kind
Feature
Kind
Proposal
Kind
Security
Kind
Studio Request
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 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: studio/blender-studio-pipeline#130
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?