Separating shared vanishing points of 3d boxes is broken

Bug #1478137 reported by Diederik van Lierop
6
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

su_v (suv-lp)
tags: added: 3dbox transformations
summary: - Separting shared vanishing point of 3d boxes is broken
+ Separating shared vanishing points of 3d boxes is broken
Revision history for this message
Diederik van Lierop (mail-diedenrezi) wrote :

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::SimpleNode::changeOrder(Inkscape::XML::Node*, Inkscape::XML::Node*): assertion 'child != ref' failed

** (inkscape:3177): CRITICAL **: virtual void Inkscape::XML::SimpleNode::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

Revision history for this message
su_v (suv-lp) wrote :

Based on tests with archived builds (on OS X 10.7.5):
- not reproduced with Inkscape 0.48.5, 0.91 r13725,
- not reproduced with Inkscape 0.91+devel rev <= 13781,
- reproduced with Inkscape 0.91+devel rev >= 13784;
the unexpected transformation of one of the 3dboxes seems related to changes in:
Revision 13784: Store 3d box tool coordinates stored in 'user units'.
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/13784

Changed in inkscape:
importance: Undecided → Medium
milestone: none → 0.92
status: New → Confirmed
tags: added: regression units
removed: transformations
Revision history for this message
su_v (suv-lp) wrote :

The console messages from 'GLib-GObject' have been noted in earlier reports too:
bug #1235369, bug #1400702, bug #1447494

The ones about Inkscape::XML::SimpleNode::changeOrder() AFAICT only happen with more recent trunk builds:
Based on tests with archived builds:
- not present with 0.91+devel rev <= 14137,
- present with 0.91+devel rev >= 14142;
they are possibly related to the changes in rev 14142 (Fix for bug #1194091):
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/14142

Revision history for this message
su_v (suv-lp) wrote :

Unsurprisingly, the scaling and displacement of the one 3dbox - which is expected to keep the unmodified perspective based on the initial position of the vanishing points - is not triggered when applying the 'steps to reproduce' in new documents based on 'px' templates (e.g. 'default px').

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.