Separating shared vanishing points of 3d boxes is broken
Bug #1478137 reported by
Diederik van Lierop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Steps to reproduce:
1) Draw a 3D box
2) Draw another 3D box -> both boxes will share the vanishing points
3) Press SHIFT, and drag one of the vanishing boxes
One of the boxes will transform properly, while the other will jump to a wrong transformation
Expected behavior: only one 3D box deforms, the other should stay put.
Inkscape rev. 14253 on Fedora 22
tags: | added: 3dbox transformations |
summary: |
- Separting shared vanishing point of 3d boxes is broken + Separating shared vanishing points of 3d boxes is broken |
To post a comment you must log in.
Not sure if this is related but this is printed to the command line when creating a 3D box:
** (inkscape:3177): CRITICAL **: virtual void Inkscape: :XML::SimpleNod e::changeOrder( Inkscape: :XML::Node* , Inkscape: :XML::Node* ): assertion 'child != ref' failed
** (inkscape:3177): CRITICAL **: virtual void Inkscape: :XML::SimpleNod e::changeOrder( Inkscape: :XML::Node* , Inkscape: :XML::Node* ): assertion 'child != ref' failed
Next, after a second 3D box has been drawn and while SHIFT-dragging the vanishing point:
(inkscape:3177): GLib-GObject- WARNING **: instance of invalid non-instantiatable type '(null)'
(inkscape:3177): GLib-GObject- CRITICAL **: g_signal_ handlers_ disconnect_ matched: assertion 'G_TYPE_ CHECK_INSTANCE (instance)' failed