Image as empty: how to get rid of it ? #39564

New Issue

Gwenael Le Page · 2014-04-02T18:28:03+02:00

Gwenael Le Page commented

2014-04-02 18:28:03 +02:00

Hello again,

sorry, it seems i keep finding new tiny bugs.

I use Blender 2.70 2c00ecc from buildbot 64bits windows (standard version)

Create new file
Add empty
Properties panel, select data panel
Choose image as display type
Open an image. I took anything, from my desktop.

1st thing:there is no way to unlink the datablock there…
Now revert back to Plain axes

It's now working in the viewport, but the icon for the data panel didn't revert to the usual one, and just below that it still shows "Empty > ImageName".

Now if you open a UV editor, you'll see that the image isn't tagged as having 0 user, although you reverted to "Plain axes"

If you save and re-open that file, the image is still available in the UV editor, although not used by the empty. It is basically impossible to get rid of this datablock, though you can replace the image by another one…

Hello again, sorry, it seems i keep finding new tiny bugs. I use Blender 2.70 2c00ecc from buildbot 64bits windows (standard version) Create new file Add empty Properties panel, select data panel Choose image as display type Open an image. I took anything, from my desktop. 1st thing:there is no way to unlink the datablock there… Now revert back to Plain axes It's now working in the viewport, but the icon for the data panel didn't revert to the usual one, and just below that it still shows "Empty > ImageName". Now if you open a UV editor, you'll see that the image isn't tagged as having 0 user, although you reverted to "Plain axes" If you save and re-open that file, the image is still available in the UV editor, although not used by the empty. It is basically impossible to get rid of this datablock, though you can replace the image by another one…

Gwenael Le Page commented

2014-04-02 18:28:03 +02:00

Changed status to: 'Open'

Gwenael Le Page commented

2014-04-02 18:28:03 +02:00

Added subscriber: @gwentiv

Willi commented

2014-04-02 19:28:35 +02:00

Added subscriber: @willi-2

Willi commented

2014-04-02 19:28:35 +02:00

This thread of mine with the same question should answer it: (in short: press Shift+LMB in image editor to set users to zero)
http://blenderartists.org/forum/showthread.php?288450-Remove-unlink-image-from-empty

IMO, regarding the empty properties, it's a missing feature (that I also missed) but not a bug.

This thread of mine with the same question should answer it: (in short: press Shift+LMB in image editor to set users to zero) http://blenderartists.org/forum/showthread.php?288450-Remove-unlink-image-from-empty IMO, regarding the empty properties, it's a missing feature (that I also missed) but not a bug.

Gwenael Le Page commented

2014-04-02 21:58:23 +02:00

Well, not being able to unlink to a datablock is maybe a missing feature, but it is the kind of things that make Blender look unpolished. One should be able to unlink that image, really.

The Shift+LMB is a nice trick, but one shouldn't have to roam forums or bugtrackers to learn how to unlink an image to an empty, should we ?

To me, Blender still pointing to that image when you have reverted to Plain axes IS a bug:
http://glp.lescigales.org/it/blender/bug%20image%20empty.jpg

Well, not being able to unlink to a datablock is maybe a missing feature, but it is the kind of things that make Blender look unpolished. One should be able to unlink that image, really. The Shift+LMB is a nice trick, but one shouldn't have to roam forums or bugtrackers to learn how to unlink an image to an empty, should we ? To me, Blender still pointing to that image when you have reverted to Plain axes IS a bug: http://glp.lescigales.org/it/blender/bug%20image%20empty.jpg ![bug_image_empty.jpg](https://archive.blender.org/developer/F83803/bug_image_empty.jpg)

Bastien Montagne commented

2014-04-02 21:59:31 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2014-04-02 21:59:31 +02:00

Bastien Montagne self-assigned this 2014-04-02 21:59:31 +02:00

Bastien Montagne commented

2014-04-02 21:59:31 +02:00

As @willi-2 said, we might do better, but not a bug in any case. :)

Gwenael Le Page commented

2014-04-02 22:11:50 +02:00

Really ?

But then why does it still show that i use the image whereas I actually use Plain axes ?
(see uploaded picture)
I have noticed that you replied just in the same time as i did. Have you seen the image Bastien ?

To me that is completely inconsistent, although very very minor.
But i don't understand how stating that you use an image as an empty while you are infact using plain axes isn't a bug… ?

Really ? But then why does it still show that i use the image whereas I actually use Plain axes ? (see uploaded picture) I have noticed that you replied just in the same time as i did. Have you seen the image Bastien ? To me that is completely inconsistent, although very very minor. But i don't understand how stating that you use an image as an empty while you are infact using plain axes isn't a bug… ?

Bastien Montagne commented

2014-04-02 22:15:35 +02:00

The "plain axes", "image" etc. are draw modes of the empty, so even in "plain axes" draw mode the empty still owns/uses the image, once it has been attributed… So yes, not ideal situation (there should be an easier way to release the image), but not considered a bug.

Bastien Montagne commented

2014-04-02 22:17:36 +02:00

Changed status from 'Archived' to: 'Open'

Bastien Montagne reopened this issue

2014-04-02 22:17:36 +02:00

Bastien Montagne commented

2014-04-02 22:17:36 +02:00

Though on second thought… will reopen anyway, at least bad user experience.

Gwenael Le Page commented

2014-04-02 22:23:38 +02:00

Yes, "unsatisfying user experience" sums it up really, as it has very little importance and doesn't lead to crashes or malfunctions but can somehow unsettle the user.

And if this one tries to find a solution by poluting the bugtracker, that's even worse !
;-)

Thanks Bastien

Yes, "unsatisfying user experience" sums it up really, as it has very little importance and doesn't lead to crashes or malfunctions but can somehow unsettle the user. And if this one tries to find a solution by poluting the bugtracker, that's even worse ! ;-) Thanks Bastien

Campbell Barton commented

2014-04-04 00:02:39 +02:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2014-04-04 00:02:39 +02:00

Campbell Barton commented

2014-04-04 00:02:39 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2014-04-04 00:02:39 +02:00

Closing again, this is a bit odd but I really prefer this isnt changed.

Attempting to clear the image when changing types can backfire.

Since scripts may set the image data before the draw type, and any UI changes would presumably have to make the interface behave differently to Python.

We have a very similar case with dupli-groups, where you can set the group, then change the dupli-type to None.

Such issues should be solved on a design level if we do try solve then, not on one-off instanced which would make blenders data assignment inconsistent.

Closing again, this is a bit odd but I really prefer this isnt changed. Attempting to clear the image when changing types can backfire. Since scripts may set the image data before the draw type, and any UI changes would presumably have to make the interface behave differently to Python. We have a very similar case with dupli-groups, where you can set the group, then change the dupli-type to `None`. Such issues should be solved on a design level if we do try solve then, not on one-off instanced which would make blenders data assignment inconsistent.

Gwenael Le Page commented

2014-04-04 09:14:26 +02:00

Fair enough Campbell, I probably didn't realise it had deep implications.
I never noticed anything with the dupligroup in fact…

As an end-user, it is just a bit off-putting and participate to the somewhat "unpolished" aspect of Blender.

Thanks to you all for your time.

Gwen

Fair enough Campbell, I probably didn't realise it had deep implications. I never noticed anything with the dupligroup in fact… As an end-user, it is just a bit off-putting and participate to the somewhat "unpolished" aspect of Blender. Thanks to you all for your time. Gwen

Campbell Barton commented

2014-04-04 11:13:40 +02:00

@gwentiv

agree its a bit unpolished - but its also not a bug (the feature works as originally intended)

perhaps the outliner could only show image icon when the draw type is set to Image (this way its clearer when the empty isnt showing an image) - that it has an image datablock thats not used --- we can overlook - as with dupli-group.

@gwentiv agree its a bit unpolished - but its also not a bug (the feature works as originally intended) perhaps the outliner could only show image icon when the draw type is set to `Image` (this way its clearer when the empty **isnt** showing an image) - that it has an image datablock thats not used --- we can overlook - as with dupli-group.

Gwenael Le Page commented

2014-04-04 13:33:01 +02:00

Yes, I guess it would be a step in the right direction, as the feedback the user would get would be in accordance to the steps he took regarding that empty

But again, as i said in the first post, this is really a tiny detail. So if something of the sort requires a substantial amount of time to tweak the code, I'd fully understand if none of you devs have the will to tweak it !

Yes, I guess it would be a step in the right direction, as the feedback the user would get would be in accordance to the steps he took regarding that empty But again, as i said in the first post, this is really a tiny detail. So if something of the sort requires a substantial amount of time to tweak the code, I'd fully understand if none of you devs have the will to tweak it !

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

Image as empty: how to get rid of it ? #39564