I also don't see the problem with materials, however here's another example where i see this being an issue:
When searching for a collection name you won't be able to look at the collections contents. This might also be the case when searching a scene or object.

Resolved since b1bdfb6e32b9

Looks lile a duplicate of T79275.

Note this is the case with every gizmo of type VIEW3D_GGT_tool_generic_handle_normal or VIEW3D_GGT_tool_generic_handle_free

This was probably just a typo, gizmos that use WIDGETGROUP_tool_generic_poll don't seem to be used as Active Object gizmos.

Cannot reproduce this issue. This seems to be resolved since D8587. Do you still encounter this problem @Damon Batey (voiddreamer)?

Wow that was a fast response :)
I've added that check now. Would be great if you could commit for me, also feel free do make adjustments if needed.

• Only check visible panels
• Rebase

Submitted D9012, could you take a look @Philipp Oeser (lichtwerk)? Not sure if it's okay to always check through panels performance wise....

Hey, great to see that this is solved now, thanks a lot!

• Rebase
• Remove use_local_camera property
• Synchronise cameras between v3d and scene when leaving cameraview
• Change "is_orrhographic_sideview" boolean to "active_orthographic_sideview" enum

-Rebase
-Use Menu instead of popover
-Add icon toggle to quickly switch to active camera
-Add return button when inside a cameraview
-Add sideview's to menu

In D8746#213841, @Leroy (Leroy) wrote:

Very strange design, more convenient to use ~ key,

It's not ment to replace the tilde menu.

but hope in outline editor, double-click the camera to switch.

I agree with that. With the changes to the operator that would also be possible.

@Yevgeny Makarov (jenkm) @Wo!262 (wo262) I've updated the description, it should be a bit clearer now.

There was another commit in this area yesterday: 1bc96468a144 your patch probably needs another rebase, bad timing :/
Functionality wise i'm not sure if simply picking the rightmost shader is too much of an assumption, i imagine this would fail in some common cases (e.g. main shader is inside a group or main shader is not the most right shader). Maybe it would be possible to rather store the "main" shader node before deconnecting it and then reconnecting that node, however this would probably be more complicated.

The crash happens because the operator tries to set the nodetree and path of the shader editor space. This was used because nodes were removed by calling the operator nodes.delete which was rather hacky.

Thanks to all!

Should a second person review this? Otherwise it would be great if you could commit this since i don't have access...

This was just a small typo, thanks.

-Fix typo in ensure_group_output
-rebase

@Michail Soluyanov Great to see a proper white theme as a preset! Looks like the tooltip needs some tweaking thought.

-fix typo in unregister function
-rebase

Thanks @Scott Ramsay (smramsay), updated the patch to avoid that issue.

-fix error when group has no outputs
-properly delete viewer node when inside a group
-use appropriate socket types for group outputs
-rebase

Thanks a lot, this works great now. It seams there are some leftover print statements in this commit, i get a bunch of non-descriptive text in the console:

@Campbell Barton (campbellbarton)
The Issue described in T66655 (which was merged with this Task) still persist. Looks like it is a separate issue and should be reopened.

I can reproduce this by adding a bl_info dictionary to the Ui Tool Simple template and registering it as an addon as @Rainer Trummer (aliasguru) pointed out.

This should now be ready, i tested this a bit and didn't encounter any bugs. The performance also seems okay, in some heavy production files the preview might not be as snappy but IMO still acceptable.

-avoid error when a material doesn`t have nodes
-fixed small mistake when choosing what socket to display
-make behaivor consistent when previewing the same socket in a group from diffrent materials
-rebase

-avoid some unnecessary calculations
-Support previewing a socket inside a group that is already viewed from another material
-general improvements

-Previewing a socket that is already viewed from another material is currently not directly possible, would be nice to support
-functions search_sockets and scan_nodes currently might go through a nodegroup multiple times which is not necessary

-Support previewing diffrent parts of one node group in multiple materials
-Add property to sockets so user crated sockets that happen to have the same name are ignored
-moved some specific functions inside class
-rebase

Thanks for the feedback!

-address inlined comments
-crate group output node if it doesen`t exist
-remove all sockets that aren`t immediatley needed
-general cleanup

Thanks!

In D6604#155452, @Campbell Barton (campbellbarton) wrote:

Looks good to me.

@Julian Eisel (Severin) Thanks alot for the review!

-Address mentioned issue
-Add some comments
-Rebase

In D6518#153946, @Debuk (Debuk) wrote:

I am pretty sure Regnas refers to how it is in Cinema4D. That doesn't cover all these options blender offers, but for most work its enough to have the "normal" variant. Maxon integrated the island selection into what I'd describe as the mouse core control scheme ( Mouse Buttons and Keyboard Modifier keys). Dbl clicking faces selects an island and it can be extended or substracted with shift and ctrl as modifiers. It's indeed pretty nice and fast that way, but I would NOT suggest to see that as an alternative to your idea/patch. Both input methods, your tool and such kind of shortcuts would rather complement each other well.

-Simplify changes in editmesh_select.c
-Handle mentioned IndexError when switching modes
-Rebase

@Debuk (Debuk)
I'm not sure if i understand your question correctly. The oneclick behavior comes from the mesh.select_linked_pick operator which already has a shortcut binding (L). When invoked the operator looks for the element under the mouse cursor and then does the same as the select_linked operator.