Log In
New Account
Home My Page Projects Blender 2.x BF release
Summary Activity Tracker SCM Files

Blender 2.6 Bug Tracker: Browse

[#32254] Knife tool cut through option doesn't always work

Date:
2012-08-03 21:27
Priority:
3
State:
Closed
Submitted by:
Paul R (intracube)
Assigned to:
Howard Trickey (howardt)
Category:
Mesh Modeling
Status:
Fixed / Closed
Relates to:
Duplicates:
Patches:
 
Summary:
Knife tool cut through option doesn't always work
Detailed description
Description:
'z' (cut through) option doesn't work if the user enables it after a cut line has been defined and if the user doesn't move the cursor again before confirming the line.

Steps:
1. add cube
2. edit mode
3. select all vertices
4. k, left mouseclick + drag to define cut line across the cube
5. z (enable cut through) - shows as enabled in UI
6. without moving cursor, leftclick again to confirm line
7. [enter] to make cut

Result:
z option is ignored - even though the viewport header displays "cut through (On)". *If the mouse is moved between steps 5 and 6, changes to the z option are updated*.

Repeatable:
Always

Blender versions (linux, x86_64):
2.63a (official) r46461
2.64 (testbuild1) r48802

Followup

Message
  • Date: 2012-09-18 16:32
  • Sender: Antony Riakiotakis
  • Hi, you should really press z -before- cutting.
  • Date: 2012-09-18 17:14
  • Sender: Howard Trickey
  • This seems like a pretty minor bug, since it easily worked around by making sure to hit z before reaching the final position for the cut line. But it is probably pretty easy to recalculate the current state (and, therefore, different cuts) as soon as z is hit. Not sure we should try to do this in current bcon4 state though.
  • Date: 2012-09-20 18:47
  • Sender: Paul R
  • Once the 'correct' order is figured out it's a non-issue, but it's something that could confuse a new user.

    "But it is probably pretty easy to recalculate the current state (and, therefore, different cuts) as soon as z is hit."
    That sounds the best solution.

    An alternative fix might be to only allow the knife options to be modified (and only display them in the header) before the line starts to be defined. A downside to this would be a user wouldn't be able to make multiple cuts and change the settings as they go for different lines.
  • Date: 2012-09-20 23:50
  • Sender: Serj Maiorov
  • It's not a bug and quite predictable:
    The knife will cut everything if you'll start the line outside the mesh, and not at snapping it to an edge.
    By beginning it with an edge-snap it will cut through the mesh precisely *after* the beginning edge.
  • Date: 2012-09-26 11:52
  • Sender: Paul R
  • Serj Maiorov;
    What you're describing sounds unrelated to this bug. In my tests I did start the line outside the mesh (and also finished outside the mesh).
  • Date: 2012-10-22 20:53
  • Sender: Howard Trickey
  • Campbell fixed this in rev 51106 (Oct 6, 2012).
 

Attached Files:

No Files Currently Attached

Changes:

Field Old Value Date By
status_idOpen2012-10-22 20:53howardt
close_dateNone2012-10-22 20:53howardt
StatusNew2012-10-22 20:53howardt
assigned_tonone2012-09-18 16:34psy-fi