Fixes issues where the node-hider arrow overlaps the node input dots that are in close proximity when the node is in hidden mode.The node-hider arrows hit box has been scaled down and moved to the right.
Before
After
Differential D4423
Bug fix for Active area for node-hider arrow too big and overlaps node input Authored by Eitan Traurig (EitanSomething) on Feb 28 2019, 6:23 AM.
Details
Fixes issues where the node-hider arrow overlaps the node input dots that are in close proximity when the node is in hidden mode.The node-hider arrows hit box has been scaled down and moved to the right. Before
Diff Detail
Event TimelineComment Actions Is it necessary to change the size of the arrow (but_size) ? Wouldn't the problem be solved just by moving it to the right slightly? Comment Actions @Harley Acheson (harley) probably that is fine too. Do you want to take a look at it? Comment Actions
I really wasn't trying to snipe this from @Eitan Traurig (EitanSomething). It was just my gut feeling that this needed a nudge to the right only when closed, so wondered about the size change. But I haven't really looked at that code so I might be missing some important detail. However, I can look at on the weekend if need be. Comment Actions The main issue is the fact that the hit targets overlap. The arrow seems as if it is nudged too far to the left away from the header text. Probably it can be fixed also by just moving the arrow over a bit. Comment Actions There were a couple issues with this open/close button and I addressed them on this patch: Comment Actions Arrow is now moved to the right and is aligned with the location of the arrow in visible mode Comment Actions Looks good to me, but now I'm a bit confused with two solutions. @Harley Acheson (harley) is yours notably different to this? Comment Actions @Eitan Traurig (EitanSomething) There is one thing that you have missed that will explain everything... If you take a look at the section of code when it is open you will see that the hit area (basically empty button) and the drawn arrow are placed in a way that includes U.widget_unit. U.widget_unit is scaled up as you scale the interface up. In a nutshell it is "20" when you have the interface at "1X" scale, and 40 when at "2X" Unfortunately the code that you are changing does not use that value. So no matter what value you put in that section the button and hitarea will slide to the left as the scale is increased. If you take a look at the following it will probably make sense: Comment Actions I can't seem to replicate the hitbox moving moving to the left. Can you share a video of this phenomenon. Comment Actions The node area overlaps in the corner of the material output node, volume scatter, etc when using https://developer.blender.org/D4431 Comment Actions
Image shown below. As mentioned, If you don't scale values using U.widget_unit then a *constant* like But again, just scale it using U.widget_unit as you can see in my example, then move things around until Left is scale 1X, right is 3X. Notice how text scale up and stays in same relative position, while the arrow Comment Actions Modification of https://developer.blender.org/D4431
Comment Actions @Eitan Traurig (EitanSomething) Seems good. Say when you consider this patch done, then we can review. Cheers |