Mark/Clear seam misbehaves when executed from spacebar search menu in 3D view #38819

Closed
opened 2014-02-25 01:03:02 +01:00 by Auuman Anubis · 21 comments

System Information
Windows 7 64bit, Nvidia GT 610

Blender Version
Broken: 2.70 RC 10f4c62
Worked: 2.63

  • Mark Seam misbehaves when accessed through spacebar search, it will clear a seam instead of marking it (if clear was the last action done)

Steps:

Search "mark seam" and mark a seam.

Clear the seam manually through the "mesh" dropdown menu,

now try to execute "Mark seam" again, and it will still clear instead.

**System Information** Windows 7 64bit, Nvidia GT 610 **Blender Version** Broken: 2.70 RC 10f4c62 Worked: 2.63 - Mark Seam misbehaves when accessed through spacebar search, it will clear a seam instead of marking it (if clear was the last action done) Steps: >Search "mark seam" and mark a seam. >Clear the seam manually through the "mesh" dropdown menu, >now try to execute "Mark seam" again, and it will still clear instead.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @auuman_anubis

Added subscriber: @auuman_anubis
Author

I spend a lot of time Unwrapping objects these days, if there was a static tic-box dedicated to "mark/un-mark" edges; it would be a great benefit to my workflow. I use the search menu as a way to sort-of "spawn" a button to mark edges, but this has become a little cumbersome with this bug lol

Thanks to whoever will look into this, much appreciated :)

I spend a lot of time Unwrapping objects these days, if there was a static tic-box dedicated to "mark/un-mark" edges; it would be a great benefit to my workflow. I use the search menu as a way to sort-of "spawn" a button to mark edges, but this has become a little cumbersome with this bug lol Thanks to whoever will look into this, much appreciated :)
Dalai Felinto self-assigned this 2014-02-25 02:42:06 +01:00

Bug confirmed, looking at it.

I use the search menu as a way to sort-of "spawn" a button to mark edges,

By the way, are you familiar with the Ctrl+E menu?

Bug confirmed, looking at it. > I use the search menu as a way to sort-of "spawn" a button to mark edges, By the way, are you familiar with the Ctrl+E menu?

This issue was referenced by blender/blender-addons-contrib@d47d030275

This issue was referenced by blender/blender-addons-contrib@d47d030275f14b1c1b7a35452f9b3c841ebeb178

This issue was referenced by d47d030275

This issue was referenced by d47d030275f14b1c1b7a35452f9b3c841ebeb178

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Closed by commit d47d030275.

Closed by commit d47d030275.

Fixed now, thanks for the report

Fixed now, thanks for the report

This issue was referenced by blender/blender-addons-contrib@073a1f8f7c

This issue was referenced by blender/blender-addons-contrib@073a1f8f7c4ab28805f5e6b85db63943f7d35eb9

This issue was referenced by 073a1f8f7c

This issue was referenced by 073a1f8f7c4ab28805f5e6b85db63943f7d35eb9

Added subscriber: @ideasman42

Added subscriber: @ideasman42

This isnt a bug, there are probably 100's of similar cases where an operators default behavior isnt exactly as you expect based on previous execution.

This is made a little more confusing when the some operator has an option to perform the opposite action (like a parent opeator with the uption to un-parent),.

even so, operators are configured to execute sensibly from the keymaps, toolbars and menus.
running operators from the search popup has mixed results.

An alternative could be never to re-use an operators last used settings whenever its executed from the search popup.

This isnt a bug, there are probably 100's of similar cases where an operators default behavior isnt exactly as you expect based on previous execution. This is made a little more confusing when the some operator has an option to perform the opposite action (like a parent opeator with the uption to un-parent),. even so, operators are configured to execute sensibly from the keymaps, toolbars and menus. running operators from the search popup has mixed results. An alternative could be never to re-use an operators last used settings whenever its executed from the search popup.
Author

I see, I like the alternative that you presented Campbell, (operators never using last settings, whenever it's executed from the search) because this would give a constant result when the command is executed (instead of appearing 'random' if the user doesn't understand why the same command yield a different result).

I would rather just use the hotkey, but I need a hand free for my morning tea :)
It would help if the hotkeys were included in the tool tips, and next to the items in the search pop-up. (this is how I learned Photoshops hotkeys)

I see, I like the alternative that you presented Campbell, (operators never using last settings, whenever it's executed from the search) because this would give a constant result when the command is executed (instead of appearing 'random' if the user doesn't understand why the same command yield a different result). I would rather just use the hotkey, but I need a hand free for my morning tea :) It would help if the hotkeys were included in the tool tips, and next to the items in the search pop-up. (this is how I learned Photoshops hotkeys)
Author

Perhaps the actions can be separated in the search pop-up.

Clear Seam being listed as a separate item from Mark Seam in search, allowing for constant results when either are selected?

Perhaps the actions can be separated in the search pop-up. Clear Seam being listed as a separate item from Mark Seam in search, allowing for constant results when either are selected?

@auuman_anubis,

Hotkeys are included in tooltips and the search popup.

the issues is internal functionality often doesn't make sense to split up into many operators, said differently, operators are not designed primarily to be accessed from the search popup.

How operators work is general design we can always improve on, but not a bug.

@auuman_anubis, Hotkeys are included in tooltips and the search popup. the issues is internal functionality often doesn't make sense to split up into many operators, said differently, operators are not designed primarily to be accessed from the search popup. How operators work is general design we can always improve on, but not a bug.
Author

Not for mark, and clear seam. I'm looking at the list right now, no hot key included in the tooltip for seam marking.
mark_seam.png

back on the search pop up, I thought this was a bug because this was a new behavior that wasn't present in 2.63

Not for mark, and clear seam. I'm looking at the list right now, no hot key included in the tooltip for seam marking. ![mark_seam.png](https://archive.blender.org/developer/F78981/mark_seam.png) back on the search pop up, I thought this was a bug because this was a new behavior that wasn't present in 2.63
Author

I don't mean to push it one way or the other, I'm still learning and I appreciate all that's been done :)

Thank you for looking into this :)

I don't mean to push it one way or the other, I'm still learning and I appreciate all that's been done :) Thank you for looking into this :)

The tooltip is for the menu (Ctrl+E),

While looking into this report I noticed some odd operators showing up in the search popup :)

Committed 497e1de25b ece755ffe6 d2548f561c

The tooltip is for the menu (Ctrl+E), While looking into this report I noticed some odd operators showing up in the search popup :) Committed 497e1de25b ece755ffe6 d2548f561c

Added subscriber: @ZsoltStefan

Added subscriber: @ZsoltStefan

@ideasman42
"...operators are not designed primarily to be accessed from the search popup."

Then what is the search for? It's only functionality is direct access to the operators.

There is one 3D application I used to use, with a pretty cool search function. Searching for a tool/operator opened up the menu or toolbar where the tool was and highlighted the tool (actually used a sort of floating tooltip with a large arrow pointing at it), so users could learn where the tools/operators can be accessed. Otherwise they would keep on using the search.

@ideasman42 "...operators are not designed primarily to be accessed from the search popup." Then what is the search for? It's only functionality is direct access to the operators. There is one 3D application I used to use, with a pretty cool search function. Searching for a tool/operator opened up the menu or toolbar where the tool was and highlighted the tool (actually used a sort of floating tooltip with a large arrow pointing at it), so users could learn where the tools/operators can be accessed. Otherwise they would keep on using the search.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#38819
No description provided.