NLA track option buttons can be interacted with even when hidden #97529

Closed
opened 2022-04-22 02:28:02 +02:00 by Colin Basnett · 12 comments
Member

System Information
Operating system: Windows 10
Graphics card: NVIDIA GTX 1070

Blender Version
Broken: 3.1
Worked: Probably never

Short description of error
The NLA track options (mute & lock) are able to be interacted with even when they have been hidden as a result of another track being "solo'd".

solowhatareyadoinbud.gif

I'm not sure why these elements are being hidden when other tracks are in solo mode. I think the solution here is to just not hide these options.

Exact steps for others to reproduce the error

  1. Make a bunch of NLA tracks
  2. "Solo" one of the tracks
  3. Click around where the mute & lock buttons used to be on non-solo'd tracks
**System Information** Operating system: Windows 10 Graphics card: NVIDIA GTX 1070 **Blender Version** Broken: 3.1 Worked: Probably never **Short description of error** The NLA track options (mute & lock) are able to be interacted with even when they have been hidden as a result of another track being "solo'd". ![solowhatareyadoinbud.gif](https://archive.blender.org/developer/F13015138/solowhatareyadoinbud.gif) I'm not sure why these elements are being hidden when other tracks are in solo mode. I think the solution here is to just not hide these options. **Exact steps for others to reproduce the error** 1. Make a bunch of NLA tracks 2. "Solo" one of the tracks 3. Click around where the mute & lock buttons used to be on non-solo'd tracks
Author
Member

Added subscriber: @cmbasnett

Added subscriber: @cmbasnett
Member

Added subscriber: @BClark

Added subscriber: @BClark
Member

Great bug find.

I expect the UI change that does the solo to lock selection (meaning it should completely lock away the interaction with those buttons.

Right now it seems to "hide" the display only visually /theme change.

Great bug find. I expect the UI change that does the solo to lock selection (meaning it should completely lock away the interaction with those buttons. Right now it seems to "hide" the display only visually /theme change.
Author
Member

In #97529#1344869, @BClark wrote:
I expect the UI change that does the solo to lock selection (meaning it should completely lock away the interaction with those buttons.

Other software (specifically audio software like Reaper) allows you to interact with the mute/solo status of all tracks regardless of the status of other tracks. I don't know why Blender users would want to hide these controls hidden; it just creates a hassle for the user because the muting/soloing have to be done in a specific order otherwise the buttons mysteriously disappear on you.

> In #97529#1344869, @BClark wrote: > I expect the UI change that does the solo to lock selection (meaning it should completely lock away the interaction with those buttons. Other software (specifically audio software like Reaper) allows you to interact with the mute/solo status of all tracks regardless of the status of other tracks. I don't know why Blender users would want to hide these controls hidden; it just creates a hassle for the user because the muting/soloing have to be done in a specific order otherwise the buttons mysteriously disappear on you.
Member

Yeah, I think not hiding everything and just doing a shade change would be better than hiding all the other tracks and buttons. In the code can you tell if it is just an overlay or it is really turning off the display of the buttons?

Yeah, I think not hiding everything and just doing a shade change would be better than hiding all the other tracks and buttons. In the code can you tell if it is just an overlay or it is really turning off the display of the buttons?

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Member

Alright, did some light investigation here. There's two different problems.

One is the UX problem that the buttons are made hidden when they shouldn't be. This can be easily changed by removing this bit of code in acf_nlatrack_setting_valid:

        /* is track enabled for solo drawing? */
        if ((adt) && (adt->flag & ADT_NLA_SOLO_TRACK)) {
          if (nlt->flag & NLATRACK_SOLO) {
            /* ok - we've got a solo track, and this is it */
            return true;
          }
          /* not ok - we've got a solo track, but this isn't it, so make it more obvious */
          return false;
        }

The second and more insidious bug is that you can interact with buttons that frankly shouldn't even be there. As far as I can tell, the buttons shouldn't be rendered or added to the UI scene, so I'm not clear as to how this is happening. Will pick this up later.

Alright, did some light investigation here. There's two different problems. One is the UX problem that the buttons are made hidden when they shouldn't be. This can be easily changed by removing this bit of code in `acf_nlatrack_setting_valid`: ``` /* is track enabled for solo drawing? */ if ((adt) && (adt->flag & ADT_NLA_SOLO_TRACK)) { if (nlt->flag & NLATRACK_SOLO) { /* ok - we've got a solo track, and this is it */ return true; } /* not ok - we've got a solo track, but this isn't it, so make it more obvious */ return false; } ``` The second and more insidious bug is that you can interact with buttons that frankly shouldn't even be there. As far as I can tell, the buttons shouldn't be rendered or added to the UI scene, so I'm not clear as to how this is happening. Will pick this up later.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Weird.
This does not go through achannel_setting_flush_widget_cb.
This does not got through ANIM_channel_setting_set.
Instead, this has an additional handling in mouse_nla_channels

Assume this could go all together? (or at least should be checked with something like bAnimChannelType->has_setting)

Weird. This does not go through `achannel_setting_flush_widget_cb`. This does not got through `ANIM_channel_setting_set`. Instead, this has an additional handling in [mouse_nla_channels ](https://developer.blender.org/diffusion/B/browse/master/source/blender/editors/space_nla/nla_channels.c$224) Assume this could go all together? (or at least should be checked with something like `bAnimChannelType`->`has_setting`)
Author
Member

mouse_nla_channels is still responsible for actually selecting channels. The more modern button system doesn't handle that.

If I nullify the mouse_nla_channels function (by just throwing a return at the top), all the buttons (solo, mute, lock) work as expected, but I am unable to select the channel.

Presumably we could just pull out the button handling code. This code note even implies as much:

 * NOTE: eventually,
 * this should probably be phased out when many of these things are replaced with buttons

I'll see what I can do to surgically remove this from that function while keeping everything else intact.

`mouse_nla_channels` is still responsible for actually selecting channels. The more modern button system doesn't handle that. If I nullify the `mouse_nla_channels` function (by just throwing a return at the top), all the buttons (solo, mute, lock) work as expected, but I am unable to select the channel. Presumably we could just pull out the button handling code. This code note even implies as much: ``` * NOTE: eventually, * this should probably be phased out when many of these things are replaced with buttons ``` I'll see what I can do to surgically remove this from that function while keeping everything else intact.

This issue was referenced by 4ac6177b8d

This issue was referenced by 4ac6177b8d676d9e678126af71067cad3674ff3b

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Sybren A. Stüvel self-assigned this 2022-05-09 12:17:06 +02:00
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
6 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#97529
No description provided.