Moving GPencil frames in time with python causes viewport issues #83590

New Issue

Tom Viguier · 2020-12-09T14:17:56+01:00

Tom Viguier commented

2020-12-09 14:17:56 +01:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.96

Blender Version
Broken: version: 2.91.0, branch: master, commit date: 2020-11-25 08:34, hash: 0f45cab862
Worked: (newest version of Blender that worked as expected)

Short description of error
While changing Grease Pencil frames 'frame_number' attribute, the viewport doesn't update well, when switching their order (needs manual action to complete that refresh/sort)

My guess is that the frames indices have to be recalculated because displaying frames- [x] before frames- [x] is confusing Blender. See here : previous bug report

Exact steps for others to reproduce the error

Open the attached .blend file,
GP_Dopesheet_bug.blend

First take a look at the two frames at time 1 an 10 (happy and angry monkey)
select the monkey and run the short script,

it gets the frames at time 1 and 10 (called frame_1 and frame_10)
and switch the frames order :

  frame_1.frame_number = 10
  frame_10.frame_number = 1

at first, it seems like nothing changed, (frame_1 displayed from time 1 to 9, frame_10 from 10)

manually click on a frame symbol in the grease pencil dopesheet,
now it looks like frame_10 is displayed all along the timeline

manually move a frame symbol along the timeline (you can even replace it at time 1 )
now everything is as expected, (frame_10 displayed from time 1 to 9, frame_1 from 10)

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.96 **Blender Version** Broken: version: 2.91.0, branch: master, commit date: 2020-11-25 08:34, hash: `0f45cab862` Worked: (newest version of Blender that worked as expected) **Short description of error** While changing Grease Pencil frames 'frame_number' attribute, the viewport doesn't update well, when switching their order (needs manual action to complete that refresh/sort) My guess is that the frames indices have to be recalculated because displaying frames- [x] before frames- [x] is confusing Blender. See here : [previous bug report ](https://developer.blender.org/rBba26adee0c5caa6d4f3ffbda9c7038e807e3f9d2) **Exact steps for others to reproduce the error** Open the attached .blend file, [GP_Dopesheet_bug.blend](https://archive.blender.org/developer/F9497137/GP_Dopesheet_bug.blend) First take a look at the two frames at time 1 an 10 (happy and angry monkey) select the monkey and run the short script, it gets the frames at time 1 and 10 (called frame_1 and frame_10) and switch the frames order : ``` frame_1.frame_number = 10 frame_10.frame_number = 1 ``` at first, it seems like nothing changed, (frame_1 displayed from time 1 to 9, frame_10 from 10) manually click on a frame symbol in the grease pencil dopesheet, now it looks like frame_10 is displayed all along the timeline manually move a frame symbol along the timeline (you can even replace it at time 1 ) now everything is as expected, (frame_10 displayed from time 1 to 9, frame_1 from 10)

Tom Viguier commented

2020-12-09 14:17:56 +01:00

Added subscriber: @Tomreggae

Tom Viguier commented

2020-12-09 14:19:09 +01:00

This comment was removed by @Tomreggae

*This comment was removed by @Tomreggae*

Antonio Vazquez self-assigned this 2020-12-09 15:27:09 +01:00

Antonio Vazquez commented

2020-12-09 15:27:09 +01:00

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

Antonio Vazquez commented

2020-12-09 15:35:11 +01:00

The frame number is not designed to be used in this way. The correct way to do this is to replace the strokes or replace the entire frame, but not just change the frame number. There are many things that happen under the hood and they cannot be changed as easily as it seems.

Antonio Vazquez commented

2020-12-09 15:43:51 +01:00

Changed status from 'Confirmed' to: 'Archived'

Antonio Vazquez closed this issue

2020-12-09 15:43:51 +01:00

Antonio Vazquez commented

2020-12-09 15:43:51 +01:00

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Tom Viguier commented

2020-12-09 15:50:51 +01:00

Thanks for your quick answer !
I 'll find another way !

Thanks for your quick answer ! I 'll find another way !

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Moving GPencil frames in time with python causes viewport issues #83590