annotation association is lost more than one level down in nested groups. #77294

New Issue

michael campbell · 2020-06-03T08:12:07+02:00

michael campbell commented

2020-06-03 08:12:07 +02:00

System Information
Operating system: Windows-10-10.0.17763-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92

Blender Version
Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-06-02 22:21, hash: 2e52b3206c
Worked: (newest version of Blender that worked as expected)

Short description of error
annotations stop working in nested groups

Exact steps for others to reproduce the error

Create a compositor and add an annotation.
draw something on the top level
create any node and put it inside a group
draw something inside that group
come back to the top level and notice your original annotation is still as it was
now group the group
go back inside and draw something in the new group
now go inside the group which is inside the group and notice that the modifications you made to the first group are also in here

**System Information** Operating system: Windows-10-10.0.17763-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92 **Blender Version** Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-06-02 22:21, hash: `2e52b3206c` Worked: (newest version of Blender that worked as expected) **Short description of error** annotations stop working in nested groups **Exact steps for others to reproduce the error** Create a compositor and add an annotation. draw something on the top level create any node and put it inside a group draw something inside that group come back to the top level and notice your original annotation is still as it was now group the group go back inside and draw something in the new group now go inside the group which is inside the group and notice that the modifications you made to the first group are also in here

michael campbell commented

2020-06-03 08:12:07 +02:00

Added subscriber: @3di

ChristopherAnderssarian commented

2020-06-03 15:16:05 +02:00

Closed as duplicate of #63481

ChristopherAnderssarian closed this issue

2020-06-03 15:16:05 +02:00

ChristopherAnderssarian commented

2020-06-03 15:16:09 +02:00

Added subscriber: @ChristopherAnderssarian

ChristopherAnderssarian commented

2020-06-03 15:16:09 +02:00

It's a known issue, the only work around is to make seperate annotation layers for each node group currently

michael campbell commented

2020-06-03 18:09:24 +02:00

Hi @ChristopherAnderssarian , I'm not sure this is exactly the same, because in the compositor it doesn't leak into the top level layer, and creating a seperate annotation layer for nested groups also doesn't work.

ChristopherAnderssarian commented

2020-06-03 19:12:38 +02:00

Could you add some more detail to the report then, functionality is very limited in this area and I'm not quite understanding what the expected result is.

modifications you made to the first group are also in here is expected behaviour (see: #63481#838635)

Could you add some more detail to the report then, functionality is very limited in this area and I'm not quite understanding what the expected result is. `modifications you made to the first group are also in here` is expected behaviour (see: #63481#838635)

michael campbell commented

2020-06-03 20:54:03 +02:00

2020-06-03 19-49-09.mp4

[2020-06-03 19-49-09.mp4](https://archive.blender.org/developer/F8574780/2020-06-03_19-49-09.mp4)

ChristopherAnderssarian commented

2020-06-03 22:14:48 +02:00

Added subscriber: @antoniov

ChristopherAnderssarian commented

2020-06-03 22:14:48 +02:00

Ah, I see what you mean, but I can't see how that's happening, unless there is an offset like this:
offset_annotations.blend
(zoom out to see what I mean)
To my knowledge annotations don't behave like that, though I could be mistaken.
But I've asked @antoniov to clarify what should exactly be the case.
I closed as duplicate as it looked to be the same underlying cause as #63481.

Ah, I see what you mean, but I can't see how that's happening, unless there is an offset like this: [offset_annotations.blend](https://archive.blender.org/developer/F8574905/offset_annotations.blend) (zoom out to see what I mean) To my knowledge annotations don't behave like that, though I could be mistaken. But I've asked @antoniov to clarify what should exactly be the case. I closed as duplicate as it looked to be the same underlying cause as #63481.

Antonio Vazquez commented

2020-06-04 08:10:09 +02:00

The annotation works by area of the screen. When you open a group, you are still in the same area, so all annotations you add will be visible in the area and maybe the position is not the correct. To do what you want, we would have to change all internal design to support annotations at group level.

michael campbell commented

2020-06-04 08:33:24 +02:00

Hi @antoniov , how is it currently working on two levels as shown in the video above if it's only tied to screen area?

ChristopherAnderssarian commented

2020-06-04 15:17:50 +02:00

@3di Can you make a .blend from factory settings showing this behaviour?

michael campbell commented

2020-06-04 23:45:29 +02:00

@ChristopherAnderssarian hmm, it seems after resetting to factory defaults I can only get it working on one level as @antoniov suggested. It must have been that my main compositor wasnt centred in my startup.blend, so presumably once inside a new group the compositor is centred properly which caused the annotation from the top level to be off screen due to position mismatch between the top level and the group level........so I guess a very ugly workaround of moving each level until the previous levels annotation is off screen can be used at least :)

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

annotation association is lost more than one level down in nested groups. #77294