blender
/
blender
129
398
Fork 572
Code Issues 6.2k Pull Requests 747 Projects 19 Wiki Activity

UI: Cleanup Dialog to Manage Orphaned Data #106653

Merged
Harley Acheson merged 22 commits from Harley/blender:ManageData into main 2024-01-17 01:09:21 +01:00
Conversation 15 Commits 22 Files Changed 5 +273 -33
Harley Acheson commented 2023-04-07 03:45:58 +02:00
Member
Copy Link

Creates a new "Cleanup" dialog that allows purging unused data blocks,
as well as a window used for managing unused data blocks.

Whether or not we keep, change, or improve our practice of removing unused data-blocks, we need tools that allow users to more easily select what to keep and delete.

The File/Cleanup menu confusingly contains six items that all call the same operator in different ways. They each remove unused data but there is one for local only, linked only, and one where you have to assume does both. And for all three there is an alternative that adds the word "Recursive" without much explanation. The tooltip description for all six is identical: "Clear all orphaned data-blocks without any users from the file". Even this text is confusing as "orphans" have no parents, while these are just without owner.

Once you decide which of the six items to select, you are then presented with an ugly confirmation dialog:

PurgeNow.gif

This patch replaces all six menu items with one item. And also adds a new item:

image

"Purge Unused Data..." gives you a single dialog where you can delete any type of unused data, in a manner that I think is more informative:

image

"Manage Unused Data..." brings up a window with Outliner in "Orphan Data" mode so that you can have more fine-grained control:

ManageUnusedWindow.png

Creates a new "Cleanup" dialog that allows purging unused data blocks, as well as a window used for managing unused data blocks. --- Whether or not we keep, change, or improve our practice of removing unused data-blocks, we need tools that allow users to more easily select what to keep and delete. The File/Cleanup menu confusingly contains **six items** that all call the *same operator* in different ways. They each remove unused data but there is one for local only, linked only, and one where you have to assume does both. And for all three there is an alternative that adds the word "Recursive" without much explanation. The tooltip description for all six is identical: "Clear all orphaned data-blocks without any users from the file". Even this text is confusing as "orphans" have no parents, while these are just without owner. Once you decide which of the six items to select, you are then presented with an ugly confirmation dialog: ![PurgeNow.gif](/attachments/2215c25b-2cec-4816-b54c-bd7e65dd7b4c) This patch replaces all six menu items with **one** item. And also adds a new item: ![image](/attachments/9733ea9b-a181-48a3-8b6d-9cce3351cdee) "Purge Unused Data..." gives you a single dialog where you can delete any type of unused data, in a manner that I think is more informative: ![image](/attachments/60f0f93f-4fea-48e5-826a-54f7c9869055) "Manage Unused Data..." brings up a window with Outliner in "Orphan Data" mode so that you can have more fine-grained control: ![ManageUnusedWindow.png](/attachments/6e05b83f-8f18-45d0-b9b4-3938ab03a531)
CleanUp.gif
71 KiB
image.png
26 KiB
PurgeNow.gif
160 KiB
image.png
40 KiB
image.png
26 KiB
image.png
26 KiB
image.png
27 KiB
image.png
26 KiB
image.png
26 KiB
image.png
38 KiB
image.png
26 KiB
ManageUnusedWindow.png
178 KiB
image.png
27 KiB
CleanUp.gif image.png image.png image.png image.png image.png image.png image.png image.png
👍 10 ❤️ 10 🚀 1
Harley Acheson added this to the User Interface project 2023-04-07 03:46:26 +02:00
Harley Acheson force-pushed ManageData from e9fd0fc516 to 05a9dbf8ef 2023-05-18 19:36:48 +02:00 Compare
Harley Acheson changed title from WIP: Managing Orphaned Data to UI: Cleanup Dialog to Manage Orphaned Data 2023-05-18 19:38:14 +02:00
Nika Kutsniashvili commented 2023-05-19 22:30:55 +02:00
Contributor
Copy Link

Hello Harley, I like this mock-up very much. I have developed add-on for more precise purging that is somewhat popular. I thought I'd share this with you so that maybe you can get some ideas from add-on inside this patch.

https://blendermarket.com/products/deep-clean

This is the add-on, if you're interested I'll send you free copy.

  1. Even with your patch Blender gives you only option to either purge all, or one-by-one. I think there should be a middle ground here, which I've done, that purges only data types. This is extremely useful and I use it every day almost for purging only images when I import and try multiple PBR materials, and node groups too.

Especially with addons like BlenderKit that import lot of images and node groups and pack them into your scene feature like this is a must. Also makes the feature more accessible and less risky, because if you use Blender's purge you're always risking losing something important you accidentally left without fake user, like Mesh data or Action.

  1. I've done purge duplicates, that only purge orphaned data that have .00 in the name, very useful and single-click solution to removing duplicated object data blocks after you've played with them.

  2. Purge by Name is little more niche, but I use it very often too for images especially. Like I want to purge multiple images from one PBR texture set, but don't want to purge rest of the orphaned images I might go back to later, I purge images with "BrickWall" in the name.

Also one thing I've noticed in the images is that purging recursive option is absent in your patch (might be wrong). I think that should be kept. I wanted to implement that but currently its impossible to do "data.remove" in python recursively.

Wish you luck with this patch

Hello Harley, I like this mock-up very much. I have developed add-on for more precise purging that is somewhat popular. I thought I'd share this with you so that maybe you can get some ideas from add-on inside this patch. https://blendermarket.com/products/deep-clean This is the add-on, if you're interested I'll send you free copy. 1. Even with your patch Blender gives you only option to either purge all, or one-by-one. I think there should be a middle ground here, which I've done, that purges only data types. This is extremely useful and I use it every day almost for purging only images when I import and try multiple PBR materials, and node groups too. Especially with addons like BlenderKit that import lot of images and node groups and pack them into your scene feature like this is a must. Also makes the feature more accessible and less risky, because if you use Blender's purge you're always risking losing something important you accidentally left without fake user, like Mesh data or Action. 2. I've done purge duplicates, that only purge orphaned data that have .00 in the name, very useful and single-click solution to removing duplicated object data blocks after you've played with them. 3. Purge by Name is little more niche, but I use it very often too for images especially. Like I want to purge multiple images from one PBR texture set, but don't want to purge rest of the orphaned images I might go back to later, I purge images with "BrickWall" in the name. Also one thing I've noticed in the images is that purging recursive option is absent in your patch (might be wrong). I think that should be kept. I wanted to implement that but currently its impossible to do "data.remove" in python recursively. Wish you luck with this patch
👍 1
thin soldier commented 2023-08-16 10:12:47 +02:00
First-time contributor
Copy Link

There are times in my workflow where I put 1 or 2 of the specific options in my Quick Favorites or assign one or 2 to keyboard shortcuts.

I would prefer for the Clean Up menu to be left as is and add this feature as something new.

There are times in my workflow where I put 1 or 2 of the specific options in my Quick Favorites or assign one or 2 to keyboard shortcuts. I would prefer for the Clean Up menu to be left as is and add this feature as something new.
Harley Acheson added 1 commit 2023-08-16 18:13:16 +02:00
Harley Acheson commented 2023-08-24 18:51:44 +02:00
Author
Member
Copy Link

@thinsoldier - There are times in my workflow where I put 1 or 2 of the specific options in my Quick Favorites or assign one or 2 to keyboard shortcuts. I would prefer for the Clean Up menu to be left as is and add this feature as something new.

Good point. If we did this it wouldn't change or remove the existing operators. And we'd move these existing separate menu items somewhere else, like to Outliner. That way these items would still show up in searches so you could add them to your Quick Favorites. Everyone else could just the new pretty thing.

> @thinsoldier - There are times in my workflow where I put 1 or 2 of the specific options in my Quick Favorites or assign one or 2 to keyboard shortcuts. I would prefer for the Clean Up menu to be left as is and add this feature as something new. Good point. If we did this it wouldn't change or remove the existing operators. And we'd move these existing separate menu items somewhere else, like to Outliner. That way these items would still show up in searches so you could add them to your Quick Favorites. Everyone else could just the new pretty thing.
Harley Acheson added 2 commits 2023-08-24 19:18:53 +02:00
Harley Acheson added 1 commit 2023-09-08 23:11:21 +02:00
Pablo Vazquez added the
Module
User Interface
Interest
Pipeline, Assets & IO
 labels 2023-09-13 18:12:51 +02:00
Harley Acheson added 2 commits 2023-11-12 17:24:23 +01:00
Harley Acheson added 2 commits 2023-12-21 00:22:17 +01:00
Harley Acheson added 1 commit 2023-12-30 21:25:03 +01:00
Brecht Van Lommel requested changes 2024-01-04 01:45:15 +01:00
Brecht Van Lommel left a comment
Owner
Copy Link

This is great stuff.

@mont29, I don't remember if you approved of this design in the past, so might want to have a look.

This is great stuff. @mont29, I don't remember if you approved of this design in the past, so might want to have a look.
source/blender/editors/space_outliner/outliner_edit.cc Outdated
@ -2255,0 +2268,4 @@
static char orphans_purge_do_local = true;
static char orphans_purge_do_linked = false;
static char orphans_purge_do_recursive = false;
Brecht Van Lommel commented 2024-01-04 01:34:39 +01:00
Owner
Copy Link

UI_block_funcN_set and UI_but_funcN_set exist to avoid global variables like these. You can pass them an allocated structure with these 3 booleans, and it should be freed for when the block or button is freed.

`UI_block_funcN_set` and `UI_but_funcN_set` exist to avoid global variables like these. You can pass them an allocated structure with these 3 booleans, and it should be freed for when the block or button is freed.
Harley marked this conversation as resolved
source/blender/editors/space_outliner/outliner_edit.cc Outdated
@ -2255,0 +2353,4 @@
uiItemS(layout);
char text[1024];
DynStr *dyn_str = BLI_dynstr_new();
Brecht Van Lommel commented 2024-01-04 01:37:50 +01:00
Owner
Copy Link

Not really important since it's already working, but I think simple std::string would be preferred over DynStr for simple cases like this where performance is not an issue.

Not really important since it's already working, but I think simple `std::string` would be preferred over `DynStr` for simple cases like this where performance is not an issue.
Brecht Van Lommel commented 2024-01-05 01:07:17 +01:00
Owner
Copy Link

To be clear, I'm not expecting this to be addressed.

To be clear, I'm not expecting this to be addressed.
Harley marked this conversation as resolved
source/blender/editors/space_outliner/outliner_edit.cc Outdated
@ -2255,0 +2458,4 @@
/* identifiers */
ot->idname = "OUTLINER_OT_orphans_cleanup";
ot->name = "Remove Unused Data...";
ot->description = "Remove Unused data in the file";
Brecht Van Lommel commented 2024-01-04 01:38:28 +01:00
Owner
Copy Link

Unused -> unused for the description

Unused -> unused for the description
Harley marked this conversation as resolved
Nika Kutsniashvili commented 2024-01-04 08:28:58 +01:00
Contributor
Copy Link

Is recursive purging missing or being removed? Its more useful for me I think. Also, if there is recursive number of data blocks displayed in brackets is misleading, since 1 Material 1 Mesh can in reality be 1 Material 1 Mesh 4 Images 2 Textures 4 Brushes because that is the data that WILL become orphaned once their owners are purged and deleted with them.

Is recursive purging missing or being removed? Its more useful for me I think. Also, if there is recursive number of data blocks displayed in brackets is misleading, since 1 Material 1 Mesh can in reality be 1 Material 1 Mesh 4 Images 2 Textures 4 Brushes because that is the data that WILL become orphaned once their owners are purged and deleted with them.
Brecht Van Lommel commented 2024-01-04 11:43:39 +01:00
Owner
Copy Link

Recursive is called Indirectly Unused, and would list those images and textures.

Recursive is called Indirectly Unused, and would list those images and textures.
👍 2
Nika Kutsniashvili commented 2024-01-04 11:54:15 +01:00
Contributor
Copy Link

I like "Recursive" and "Purge" better as names. But regardless this is great design

I like "Recursive" and "Purge" better as names. But regardless this is great design
Brecht Van Lommel commented 2024-01-04 12:18:10 +01:00
Owner
Copy Link

Maybe keeping "Purge" makes sense. It does communicate the purpose a bit more, in implying that this data is probably unwanted.

"Recursive", not sure how well understood that term is by the average user, I'm too biased as a programmer to make a good guess.

Maybe keeping "Purge" makes sense. It does communicate the purpose a bit more, in implying that this data is probably unwanted. "Recursive", not sure how well understood that term is by the average user, I'm too biased as a programmer to make a good guess.
Nika Kutsniashvili commented 2024-01-04 13:55:22 +01:00
Contributor
Copy Link

I might be biased as well. But since we use recursive in api it would be nice if that was name in UI as well. Will make things more discoverable in api.

I might be biased as well. But since we use recursive in api it would be nice if that was name in UI as well. Will make things more discoverable in api.
Nika Kutsniashvili commented 2024-01-04 18:47:37 +01:00
Contributor
Copy Link

One more nitpick: In screens "Cancel" is colored and confirmation is black. Shouldn't this be vice versa? AFAIK only place we had those confirmation windows before was on saving, and there "Save" is colored, and cancel is black

One more nitpick: In screens "Cancel" is colored and confirmation is black. Shouldn't this be vice versa? AFAIK only place we had those confirmation windows before was on saving, and there "Save" is colored, and cancel is black
Harley Acheson commented 2024-01-04 18:52:34 +01:00
Author
Member
Copy Link

One more nitpick: In screens "Cancel" is colored and confirmation is black. Shouldn't this be vice versa? AFAIK only place we had those confirmation windows before was on saving, and there "Save" is colored, and cancel is black

That could certainly change. But usually my thinking is that the default button (the action that happens if you just press "Enter") should not have negative consequence if possible. So for things that could do harm if you don't read and just press "Enter" it should be the Cancel button.

> One more nitpick: In screens "Cancel" is colored and confirmation is black. Shouldn't this be vice versa? AFAIK only place we had those confirmation windows before was on saving, and there "Save" is colored, and cancel is black That could certainly change. But usually my thinking is that the default button (the action that happens if you just press "Enter") should not have negative consequence if possible. So for things that could do harm if you don't read and just press "Enter" it should be the Cancel button.
👍 3
Harley Acheson added 2 commits 2024-01-05 00:39:44 +01:00
Harley Acheson added 1 commit 2024-01-05 00:45:40 +01:00
Brecht Van Lommel approved these changes 2024-01-05 01:07:39 +01:00
source/blender/editors/space_outliner/outliner_edit.cc Outdated
@ -2255,0 +2400,4 @@
BLI_dynstr_clear(dyn_str);
orphan_desc(C, dyn_str, false, false, true);
BLI_snprintf(text, 1024, "Include Indirectly Unused (Recursive)");
Brecht Van Lommel commented 2024-01-05 01:02:46 +01:00
Owner
Copy Link

Now getting into nitpicky territory...

This is using title case while "Local data" and "Linked data" are not. "unused" is implied for "Local data" and "Linked data", so why use it here? Clarifications like "(Recursive)" are not something we normally do in the UI, that seems like it should be in the tooltip.

I suggest "Include indirect data".

Now getting into nitpicky territory... This is using title case while "Local data" and "Linked data" are not. "unused" is implied for "Local data" and "Linked data", so why use it here? Clarifications like "(Recursive)" are not something we normally do in the UI, that seems like it should be in the tooltip. I suggest "Include indirect data".
Harley marked this conversation as resolved
Harley Acheson added 1 commit 2024-01-05 01:21:32 +01:00
Harley Acheson added 1 commit 2024-01-05 01:30:01 +01:00
Harley Acheson added 1 commit 2024-01-05 01:32:59 +01:00
buildbot/vexp-code-patch-lint Build done. Details
buildbot/vexp-code-patch-linux-x86_64 Build done. Details
buildbot/vexp-code-patch-darwin-arm64 Build done. Details
buildbot/vexp-code-patch-windows-amd64 Build done. Details
buildbot/vexp-code-patch-darwin-x86_64 Build done. Details
buildbot/vexp-code-patch-coordinator Build done. Details
12dacc8238 Merge branch 'main' of projects.blender.org:blender/blender into ManageData
Harley Acheson commented 2024-01-05 01:36:04 +01:00
Author
Member
Copy Link

@blender-bot build

@blender-bot build
Bastien Montagne requested changes 2024-01-08 18:12:54 +01:00
Bastien Montagne left a comment
Owner
Copy Link

The feature from a user perspective looks great.

But the code can use some more work to make it a bit more aligned with general UI designs afaik, see comment below.

Could also use some review from people more informed about our UI codebase...

The feature from a user perspective looks great. But the code can use some more work to make it a bit more aligned with general UI designs afaik, see comment below. Could also use some review from people more informed about our UI codebase...
source/blender/editors/space_outliner/outliner_edit.cc Outdated
@ -2255,0 +2328,4 @@
else {
is_first = false;
}
desc.append<>(std::to_string(num_tagged[i]) + " ");
Bastien Montagne commented 2024-01-08 18:09:04 +01:00
Owner
Copy Link

No reason to use append on strings afaik, just use += operator?

That kind of formatting could also benefit from using fmt::format from our extern/fmtlib library.

No reason to use `append` on strings afaik, just use `+=` operator? That kind of formatting could also benefit from using `fmt::format` from our `extern/fmtlib` library.
Harley marked this conversation as resolved
source/blender/editors/space_outliner/outliner_edit.cc Outdated
@ -2255,0 +2445,4 @@
{
OrphansPurgeData *purge_data = MEM_new<OrphansPurgeData>("orphans_purge_data");
purge_data->op = op;
UI_popup_block_invoke(C, wm_block_create_orphans_cleanup, purge_data, MEM_freeN);
Bastien Montagne commented 2024-01-08 18:07:22 +01:00
Owner
Copy Link

Do not invoke modal UI items from an exec function. This code should be in the invoke callback.

The exec callback should be basically what wm_block_orphans_purge is doing currently.

Further more, any reasons not to use some operator-aware popup system, like WM_operator_props_dialog_popup or so?

That way you can also define the settings (which types of data to purge) in the operator itself - or even better, can just re-use (and extend) existing OUTLINER_OT_orphans_purge, instead of creating a new one that does the same thing?

Do not invoke modal UI items from an `exec` function. This code should be in the `invoke` callback. The `exec` callback should be basically what `wm_block_orphans_purge` is doing currently. Further more, any reasons not to use some operator-aware popup system, like `WM_operator_props_dialog_popup` or so? That way you can also define the settings (which types of data to purge) in the operator itself - or even better, can just re-use (and extend) existing `OUTLINER_OT_orphans_purge`, instead of creating a new one that does the same thing?
Harley Acheson commented 2024-01-08 21:57:56 +01:00
Author
Member
Copy Link

Do not invoke modal UI items from an exec function. This code should be in the invoke callback

Thanks! done.

any reasons not to use some operator-aware popup system, like WM_operator_props_dialog_popup or so?

Just unfamiliarity with that, so will definitely will look into that. I'm also hoping to move toward dialogs that have a clear "cancel". I don't mind if some dialogs with complex behavior are more "bespoke".

> Do not invoke modal UI items from an exec function. This code should be in the invoke callback Thanks! done. > any reasons not to use some operator-aware popup system, like WM_operator_props_dialog_popup or so? Just unfamiliarity with that, so will definitely will look into that. I'm also hoping to move toward dialogs that have a clear "cancel". I don't mind if some dialogs with complex behavior are more "bespoke".
source/blender/editors/space_outliner/outliner_edit.cc
@ -2255,0 +2460,4 @@
ot->exec = outliner_orphans_cleanup_exec;
/* flags */
ot->flag = OPTYPE_REGISTER;
Bastien Montagne commented 2024-01-08 17:53:22 +01:00
Owner
Copy Link

Missing OPTYPE_UNDO I think? Otherwise, a comment explaining why it's not needed would be good to have.

Missing `OPTYPE_UNDO` I think? Otherwise, a comment explaining why it's not needed would be good to have.
Harley marked this conversation as resolved
source/blender/editors/space_outliner/outliner_edit.cc Outdated
@ -2255,0 +2465,4 @@
static int outliner_orphans_manage_exec(bContext *C, wmOperator * /*op*/)
{
const rcti window_rect = {
Bastien Montagne commented 2024-01-08 17:52:35 +01:00
Owner
Copy Link

Would be better to adjust these default values to the available screen space? On some modern screens, 500x500 is a fairly small window...

Would be better to adjust these default values to the available screen space? On some modern screens, 500x500 is a fairly small window...
Harley marked this conversation as resolved
source/blender/editors/space_outliner/outliner_edit.cc
@ -2255,0 +2486,4 @@
SpaceOutliner *soutline = (SpaceOutliner *)CTX_wm_area(C)->spacedata.first;
soutline->outlinevis = SO_ID_ORPHANS;
}
return OPERATOR_FINISHED;
Bastien Montagne commented 2024-01-08 17:54:12 +01:00
Owner
Copy Link

Should return OPERATOR_CANCELLED if WM_window_open fails...

Should return `OPERATOR_CANCELLED` if `WM_window_open` fails...
Harley marked this conversation as resolved
Harley Acheson added 3 commits 2024-01-08 21:22:13 +01:00
Bastien Montagne commented 2024-01-09 11:33:04 +01:00
Owner
Copy Link

Another point I just realized: If you are renaming "orphan" to "unused", you should also tackle the other areas of the UI (starting with the name of the Outliner view itself).

Another point I just realized: If you are renaming "orphan" to "unused", you should also tackle the other areas of the UI (starting with the name of the Outliner view itself).
Hans Goudey reviewed 2024-01-16 17:13:19 +01:00
source/blender/editors/space_outliner/outliner_edit.cc Outdated
@ -2255,0 +2315,4 @@
UI_but_drawflag_disable(but, UI_BUT_TEXT_LEFT);
}
static std::string orphan_desc(bContext *C, bool local, bool linked, bool recursive)
Hans Goudey commented 2024-01-16 17:12:40 +01:00
Member
Copy Link

const bContext *, const bool

`const bContext *`, `const bool`
Harley marked this conversation as resolved
source/blender/editors/space_outliner/outliner_edit.cc Outdated
@ -2255,0 +2346,4 @@
static uiBlock *wm_block_create_orphans_cleanup(bContext *C, ARegion *region, void *arg)
{
OrphansPurgeData *purge_data = (OrphansPurgeData *)arg;
Hans Goudey commented 2024-01-16 17:11:27 +01:00
Member
Copy Link

Use static_cast here instead of C style cast

Use `static_cast` here instead of C style cast
Harley marked this conversation as resolved
source/blender/editors/space_outliner/outliner_edit.cc Outdated
@ -2255,0 +2446,4 @@
static int outliner_orphans_cleanup_exec(bContext *C, wmOperator *op)
{
OrphansPurgeData *purge_data = MEM_new<OrphansPurgeData>("orphans_purge_data");
Hans Goudey commented 2024-01-16 17:12:01 +01:00
Member
Copy Link

Use __func__ instead of manually choosing a string

Use `__func__` instead of manually choosing a string
Harley marked this conversation as resolved
Harley Acheson added 2 commits 2024-01-16 22:40:56 +01:00
buildbot/vexp-code-patch-lint Build done. Details
buildbot/vexp-code-patch-darwin-x86_64 Build done. Details
buildbot/vexp-code-patch-linux-x86_64 Build done. Details
buildbot/vexp-code-patch-darwin-arm64 Build done. Details
buildbot/vexp-code-patch-windows-amd64 Build done. Details
buildbot/vexp-code-patch-coordinator Build done. Details
98f5dd95b8 Changes required by review.
Harley Acheson commented 2024-01-16 22:43:29 +01:00
Author
Member
Copy Link

@blender-bot build

@blender-bot build
Harley Acheson added 1 commit 2024-01-16 23:53:51 +01:00
buildbot/vexp-code-patch-lint Build done. Details
buildbot/vexp-code-patch-linux-x86_64 Build done. Details
buildbot/vexp-code-patch-windows-amd64 Build done. Details
buildbot/vexp-code-patch-darwin-x86_64 Build done. Details
buildbot/vexp-code-patch-darwin-arm64 Build done. Details
buildbot/vexp-code-patch-coordinator Build done. Details
56c2b3b3a3 removing unused variable
Harley Acheson commented 2024-01-17 00:48:07 +01:00
Author
Member
Copy Link

@blender-bot build

@blender-bot build
Harley Acheson merged commit 58e1e88dc3 into main 2024-01-17 01:09:21 +01:00
Harley Acheson deleted branch ManageData 2024-01-17 01:09:23 +01:00
Bastien Montagne commented 2024-01-17 09:57:32 +01:00
Owner
Copy Link

Please revert that commit, this PR was not approved, and half of my feedback was not addressed (not creating a new operator when existing one should be usable, not using 'standard' operator popup code instead of defining own popup panel,...)

Please revert that commit, this PR was not approved, and half of my feedback was not addressed (not creating a new operator when existing one should be usable, not using 'standard' operator popup code instead of defining own popup panel,...)
Sign in to join this conversation.
Reviewers
No reviewers
Brecht Van Lommel
Bastien Montagne
Labels
Clear labels   
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
This issue affects/is about backward or forward 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
Issues relating to Wayland windowing support.

  
Interest
Workbench

  
Interest: X11

Issues relating to Xorg/X11 support.

  
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
Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
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 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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
User Interface
Assignees
Clear assignees
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#106653
No description provided.
Delete Branch "Harley/blender:ManageData"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?