MARK Seam/Sharp (edge) command in search menu not always MARKs (sometime it CLEARs) #38856

New Issue

Dolphin Dream · 2014-02-26T20:15:20+01:00

Dolphin Dream commented

2014-02-26 20:15:20 +01:00

System Information
Operating system and graphics card
Ubuntu 12.04 / NVIDIA GeForce 310

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional)
2.7(test build release) : Hash: 10f4c62

Short description of error
Marking and clearing sharp/seam edges.
Using the (space) search menu to "Mark Sharp/Seam" after a CLEAR sharp/seam command was executed, will not actually MARK, but CLEAR the sharp/seam edge instead.

Note: Based on a irc chat with ideaman42 he indicates that there is one operator for clear/mark edges, and the clear vs sharp is defined via a parameter. This discussion was related thought to the reason why only the Mark Sharp/Seam command is listed in the search menu, but there is none for Clear Sharp/Seam (though it should, IMO). I suspect that this missing search menu entry and this currently reported bug are related.

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

new file (cube)
tab to edit mode
select any TWO of the cube's edges
space search for Mark Sharp and execute to mark them sharp [ both edges are marked as sharp ]
select one of the two sharp edges
from the Mesh menu execute the mesh/edge/Clear Sharp [ the edge should have it's sharp mark cleared)
select the other sharp edge
space search for Mark Sharp and execute to mark the sharp [ the edge sharp status is actually cleared]

executing the menu/mark sharp on any other edge will do nothing since (i suspect) it is calling the Clear Sharp (instead of the Mark Sharp)

(same steps apply to mark/clear seam)

**System Information** Operating system and graphics card Ubuntu 12.04 / NVIDIA GeForce 310 **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) Worked: (optional) 2.7(test build release) : Hash: 10f4c62 **Short description of error** Marking and clearing sharp/seam edges. Using the (space) search menu to "Mark Sharp/Seam" after a CLEAR sharp/seam command was executed, will not actually MARK, but CLEAR the sharp/seam edge instead. Note: Based on a irc chat with ideaman42 he indicates that there is one operator for clear/mark edges, and the clear vs sharp is defined via a parameter. This discussion was related thought to the reason why only the Mark Sharp/Seam command is listed in the search menu, but there is none for Clear Sharp/Seam (though it should, IMO). I suspect that this missing search menu entry and this currently reported bug are related. **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps - new file (cube) - tab to edit mode - select any TWO of the cube's edges - space search for Mark Sharp and execute to mark them sharp [ both edges are marked as sharp ] - select one of the two sharp edges - from the Mesh menu execute the mesh/edge/Clear Sharp [ the edge should have it's sharp mark cleared) - select the other sharp edge - space search for Mark Sharp and execute to mark the sharp [ the edge sharp status is actually cleared] executing the menu/mark sharp on any other edge will do nothing since (i suspect) it is calling the Clear Sharp (instead of the Mark Sharp) (same steps apply to mark/clear seam)

Dolphin Dream commented

2014-02-26 20:15:20 +01:00

Changed status to: 'Open'

Dolphin Dream commented

2014-02-26 20:15:20 +01:00

Added subscriber: @MariusGiurgi

blender-admin commented

2014-02-26 20:56:36 +01:00

This issue was referenced by blender/blender-addons-contrib@59a0828ac1

This issue was referenced by blender/blender-addons-contrib@59a0828ac1b4a9164275f70f48ab212f5c7f1739

blender-admin commented

2014-02-26 20:56:36 +01:00

This issue was referenced by 59a0828ac1

This issue was referenced by 59a0828ac1b4a9164275f70f48ab212f5c7f1739

Brecht Van Lommel commented

2014-02-26 20:57:56 +01:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2014-02-26 20:57:56 +01:00

Brecht Van Lommel commented

2014-02-26 20:57:56 +01:00

Closed by commit 59a0828ac1.

Closed by commit 59a0828ac1.

Brecht Van Lommel commented

2014-02-26 20:59:02 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2014-02-26 20:59:02 +01:00

Thanks for the report, fixed this behavior now.

I have not added the clear seam operator to the search menu, this will require some bigger changes. At the moment clear and mark seam are a single operator with a "clear" setting you can toggle. At some point we might want to make the same operator with different settings available in the menu, but that's not supported at the moment.

Thanks for the report, fixed this behavior now. I have not added the clear seam operator to the search menu, this will require some bigger changes. At the moment clear and mark seam are a single operator with a "clear" setting you can toggle. At some point we might want to make the same operator with different settings available in the menu, but that's not supported at the moment.

Dalai Felinto commented

2014-02-26 22:35:08 +01:00

Added subscribers: @ideasman42, @dfelinto

Dalai Felinto commented

2014-02-26 22:35:08 +01:00

@brecht see related discussion: #38819 and d47d0302 (reverted here: 073a1f8f). And, well, D350
cc: @ideasman42

@brecht see related discussion: #38819 and d47d0302 (reverted here: 073a1f8f). And, well, [D350](https://archive.blender.org/developer/D350) cc: @ideasman42

Brecht Van Lommel commented

2014-02-26 23:42:29 +01:00

Ah well, in the past I have solved more such cases by simply adding PROP_SKIP_SAVE. To me that seems like the right solution in the current system, if there is a property that totally changes the tool so that the description no longer covers it, then we just don't remember it.

We could figure out a better convention, maybe always splitting this into multiple operators or somehow exposing multiple variations of an operator in the search menu. But I think that adding PROP_SKIP_SAVE is a net improvement.

Ah well, in the past I have solved more such cases by simply adding PROP_SKIP_SAVE. To me that seems like the right solution in the current system, if there is a property that totally changes the tool so that the description no longer covers it, then we just don't remember it. We could figure out a better convention, maybe always splitting this into multiple operators or somehow exposing multiple variations of an operator in the search menu. But I think that adding PROP_SKIP_SAVE is a net improvement.

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

MARK Seam/Sharp (edge) command in search menu not always MARKs (sometime it CLEARs) #38856