Inactive Snap Icon whiile snap is active #64991

New Issue

Alexander Dumproff · 2019-05-22T15:29:01+02:00

2019-05-22 15:29:01 +02:00

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: Quadro 5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 377.83

Blender Version
Broken: version: 2.80 (sub 71), branch: master, commit date: 2019-05-22 08:33, hash: 85322737ba

Short description of error
While an object is being Grabbed with - [x] when entering SnapMode with [Shift]-[Tab] Snap will be active but the Snap Icon will still be shown as inactive.

Exact steps for others to reproduce the error

Activate the Tool Settings bar on top of 3D view
Add a mesh
press - to grab but don't drop the object yet
Press [Shift]+[Tab] to activate snapping

Snap will be active but the Icon doesn't reflect it.

Even after the object is dropped to a new location snap will be active but the icon doesn't show it.

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: Quadro 5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 377.83 **Blender Version** Broken: version: 2.80 (sub 71), branch: master, commit date: 2019-05-22 08:33, hash: `85322737ba` **Short description of error** While an object is being Grabbed with - [x] when entering SnapMode with [Shift]-[Tab] Snap will be active but the Snap Icon will still be shown as inactive. **Exact steps for others to reproduce the error** 1. Activate the Tool Settings bar on top of 3D view 2. Add a mesh 3. press - [x] to grab but don't drop the object yet 4. Press [Shift]+[Tab] to activate snapping - > Snap will be active but the Icon doesn't reflect it. Even after the object is dropped to a new location snap will be active but the icon doesn't show it.

Alexander Dumproff commented

2019-05-22 15:29:01 +02:00

Added subscriber: @A.Lex_3D

Leon Eckardt commented

2019-05-22 19:40:47 +02:00

Added subscriber: @Leon95

Leon Eckardt self-assigned this 2019-05-22 19:40:47 +02:00

Leon Eckardt commented

2019-05-22 19:40:47 +02:00

Can confirm, try to fix

Leon Eckardt removed their assignment 2019-05-23 16:39:08 +02:00

Leon Eckardt commented

2019-05-23 16:39:08 +02:00

Cant find where it needs to be fixed

Brecht Van Lommel commented

2019-05-29 02:15:32 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-05-29 02:15:32 +02:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2019-05-29 02:15:32 +02:00

Brecht Van Lommel self-assigned this 2019-05-29 02:15:32 +02:00

Brecht Van Lommel commented

2019-05-29 02:15:32 +02:00

Changing settings during transform indeed does not immediately update buttons. While this could be good, there are some technical reasons for this and I would consider it more of a possible UI improvement than a bug.

Alfred Morgan commented

2020-01-26 08:15:22 +01:00

Added subscriber: @Zectbumo

Alfred Morgan commented

2020-01-26 08:15:22 +01:00

I can reproduce.

In #64991#690170, @brecht wrote:
Changing settings during transform indeed does not immediately update buttons. While this could be good, there are some technical reasons for this and I would consider it more of a possible UI improvement than a bug.

@brecht this is indeed a bug. the UI is not representing the current state.

I feel that you may have overlooked what the OP wrote: "Even after the object is dropped to a new location snap will be active but the icon doesn't show it."
This means that the UI state is out of sync after the operation is completed or canceled. This issue is clearly a bug and needs to be reopened. At the very least the snap icon should update after the operation is completed or canceled.

I can reproduce. > In #64991#690170, @brecht wrote: > Changing settings during transform indeed does not immediately update buttons. While this could be good, there are some technical reasons for this and I would consider it more of a possible UI improvement than a bug. @brecht this is indeed a bug. the UI is not representing the current state. I feel that you may have overlooked what the OP wrote: "Even after the object is dropped to a new location snap will be active but the icon doesn't show it." This means that the UI state is out of sync after the operation is completed or canceled. This issue is clearly a bug and needs to be reopened. At the very least the snap icon should update after the operation is completed or canceled.

Alfred Morgan commented

2020-01-26 10:36:02 +01:00

I found an additional detail. The snap status icon gets out of sync only for the operations where the "affect" is enabled in the snap menu. Enable affect in the snap menu for move, rotate, scale to see the results of the bug, the status icon getting out of sync.

Paul R commented

2020-01-30 07:34:11 +01:00

Added subscriber: @intracube

Paul R commented

2020-01-30 07:34:11 +01:00

I can't see how this would be classed as an improvement, feature or enhancement.

This is about core functionality - the UI should always report the true state of the underlying scene or tool in use. If not, it's a fairly clean definition of a bug.

If I can also add as a general comment; Over the years, I've noticed Blender's general architectural designs seem to allow for many cases similar to this - where the UI can get out of step with the scene or presents stale or erroneous data to the user. Even as far back as 2.3* and 2.4*, selecting objects in a specific pattern could result in the materials/texture panels appearing blank (even if a material/texture had been previously assigned) and you had to know to click away from the object and re-select to get the panels to refresh.

Issues like this can cause confusion for new and experienced users alike. Something relatively simple can trip people up and lead people to go down blind alleys. In practice, users find workarounds (often means poking part of the UI somewhere to trigger an update), but this is hit and miss and has to be learned for each unique case.

Apologies for the wordy reply.

I can't see how this would be classed as an improvement, feature or enhancement. This is about core functionality - the UI should always report the true state of the underlying scene or tool in use. If not, it's a fairly clean definition of a bug. If I can also add as a general comment; Over the years, I've noticed Blender's general architectural designs seem to allow for many cases similar to this - where the UI can get out of step with the scene or presents stale or erroneous data to the user. Even as far back as 2.3* and 2.4*, selecting objects in a specific pattern could result in the materials/texture panels appearing blank (even if a material/texture had been previously assigned) and you had to know to click away from the object and re-select to get the panels to refresh. Issues like this can cause confusion for new and experienced users alike. Something relatively simple can trip people up and lead people to go down blind alleys. In practice, users find workarounds (often means poking part of the UI somewhere to trigger an update), but this is hit and miss and has to be learned for each unique case. Apologies for the wordy reply.

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

Inactive Snap Icon whiile snap is active #64991