use_negative_frames user preference is not respected in the graph editor #44717

New Issue

Daniel Salazar · 2015-05-15T09:46:40+02:00

Daniel Salazar commented

2015-05-15 09:46:40 +02:00

System Information
Linux 64

Blender Version
Broken: ba9dbaa

Short description of error
use_negative_frames user preference is not respected in the graph editor

Exact steps for others to reproduce the error
Go to user preferences > Editing
Disable "Allow Negative Frames"

This will make the timeline never go below zero in any editor but the graph editor. Produces jumps when going back to other editors that do respect the option.

**System Information** Linux 64 **Blender Version** Broken: ba9dbaa **Short description of error** use_negative_frames user preference is not respected in the graph editor **Exact steps for others to reproduce the error** Go to user preferences > Editing Disable "Allow Negative Frames" This will make the timeline never go below zero in any editor but the graph editor. Produces jumps when going back to other editors that do respect the option.

Daniel Salazar commented

2015-05-15 09:46:40 +02:00

Changed status to: 'Open'

Daniel Salazar commented

2015-05-15 09:46:40 +02:00

Added subscriber: @zanqdo

Tobias Johansson commented

2015-05-15 14:08:26 +02:00

Added subscriber: @barfot

Tobias Johansson commented

2015-05-15 14:08:26 +02:00

What is the correct way for me as a noob to contribute with patches for a bugs? Any way, here is a patch that solves the issue
graphNegativeFrames.patch

What is the correct way for me as a noob to contribute with patches for a bugs? Any way, here is a patch that solves the issue [graphNegativeFrames.patch](https://archive.blender.org/developer/F175093/graphNegativeFrames.patch)

Aaron Carlisle commented

2015-05-15 17:54:42 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2015-05-15 17:54:42 +02:00

@barfot please make a diff here https://developer.blender.org/differential/query/all/ leaving the reviewers empty and post the link to it here

Tobias Johansson commented

2015-05-15 19:33:00 +02:00

Thanks @Blendify
My patch: https://developer.blender.org/D1303

Thanks @Blendify My patch: https://developer.blender.org/D1303

Bastien Montagne commented

2015-05-15 21:56:33 +02:00

Added subscribers: @JoshuaLeung, @Sergey, @ideasman42, @mont29

Bastien Montagne commented

2015-05-15 21:56:33 +02:00

I do not remember whether this is wanted behavior or not, Joshua?

Joshua Leung commented

2015-05-17 15:37:20 +02:00

Although I can see how the graph editor not obeying this setting could be problematic, several potential issues do need to be pointed out:

In the Graph Editor, the current frame is used for certain transform operations (e.g. scale, rotate) when set to use the "2d cursor" as the pivot point for those transforms. Not being able to set the current frame before 0 in those cases would be problematic for those cases. Granted, this is probably not used that much, so it may enough to warrant keeping the current behaviour.
Another use case that may be more problematic is for Driver FCurves. In that case, the user may want to set or snap the cursor to specific values so that the Driver FCurve can be modified or inspected with precision.

The cases pointed out here may turn out to be quite rare, in which case, requiring the user to enable the "use negative frames" option to do this is probably not a bad thing. On the other hand, the fact that this behaviour does cause some visible confusion when the behaviour don't match up between the different editors is perhaps a bigger issue, since we know that this is bound to happen.

Although I can see how the graph editor not obeying this setting could be problematic, several potential issues do need to be pointed out: - In the Graph Editor, the current frame is used for certain transform operations (e.g. scale, rotate) when set to use the "2d cursor" as the pivot point for those transforms. Not being able to set the current frame before 0 in those cases would be problematic for those cases. Granted, this is probably not used that much, so it may enough to warrant keeping the current behaviour. - Another use case that may be more problematic is for Driver FCurves. In that case, the user may want to set or snap the cursor to specific values so that the Driver FCurve can be modified or inspected with precision. The cases pointed out here may turn out to be quite rare, in which case, requiring the user to enable the "use negative frames" option to do this is probably not a bad thing. On the other hand, the fact that this behaviour does cause some visible confusion when the behaviour don't match up between the different editors is perhaps a bigger issue, since we know that this is bound to happen.

Brecht Van Lommel commented

2015-05-17 17:09:44 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2015-05-17 17:09:44 +02:00

I think similar arguments could be made for other editors where it is also convenient to go to negative frames to inspect or modify something. That's kind of why the setting exists in the first place. I would go for consistency and make the graph editor obey this setting.

blender-admin commented

2015-05-20 13:58:33 +02:00

This issue was referenced by 77ef3f9041

This issue was referenced by 77ef3f9041edea39b1d036e048a8ac35e388520d

Campbell Barton commented

2015-05-20 14:03:03 +02:00

Changed status from 'Open' to: 'Resolved'

Campbell Barton closed this issue

2015-05-20 14:03:03 +02:00

Daniel Salazar commented

2015-05-20 19:07:41 +02:00

Thank you all

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

use_negative_frames user preference is not respected in the graph editor #44717