Maniphest T69144

GPencil: Wrong behavior of object origin shifting
Closed, Resolved

Assigned To
Antonio Vazquez (antoniov)
Authored By
user1 (user1)
Aug 25 2019, 12:39 PM
Tags
  • BF Blender
  • Grease Pencil
Subscribers
Antonio Vazquez (antoniov)
Bastien Montagne (mont29)
user1 (user1)

Description

System Information
Operating system:linux mint 19
Graphics card:nvidia gt 630

Blender Version
Broken: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e, type: Release
build date: 2019-07-29, 17:17:04

Short description of error
When i try to set the origin of a grease pencil object{F7702890}
to the 3d cursor

,
instead it (the object itself) jumps back to the origin indicator
.

Exact steps for others to reproduce the error
Open blender, create a grease pencil object (e.g. a circle) with an origin not in the center of "mass", place the 3dcursor somewhere in the midle of the gp object and try to set the origin back to that cursor by: object→set origin→origin to 3d cursor.
One would expect the yellow dot that indicates the origin to move to the cursor now, but instead the object jumps back to the orgin.

Related Objects

Mentioned Here
T68202: Grease Pencil: Set Origin do not refresh until GP object is moved
rBf6cb5f54494e: Version bump to 2.80 final release

Event Timeline

user1 (user1) created this task.Aug 25 2019, 12:39 PM
Antonio Vazquez (antoniov) lowered the priority of this task from 90 to 30.Aug 25 2019, 1:15 PM
Antonio Vazquez (antoniov) added a subscriber: Antonio Vazquez (antoniov).

This was already fixed in the daily build. Could you download last version and test?

Antonio Vazquez (antoniov) renamed this task from Wrong behavior of GP object origin shifting to GPencil: Wrong behavior of object origin shifting.Aug 25 2019, 1:15 PM
Antonio Vazquez (antoniov) claimed this task.
Antonio Vazquez (antoniov) added a project: Grease Pencil.
Antonio Vazquez (antoniov) added a subscriber: Bastien Montagne (mont29).Aug 26 2019, 10:44 PM

@Bastien Montagne (mont29) If I know this was fixed, do I need keep the bug open waiting for user info or it's better close it?

Bastien Montagne (mont29) added a comment.Aug 26 2019, 11:38 PM

@Antonio Vazquez (antoniov) when you are totally sure that it has been fixed, please close (ideally with a reference to the commit that solved it).

Antonio Vazquez (antoniov) changed the task status from Unknown Status to Resolved.Aug 27 2019, 8:52 AM

This was already solved in T68202