 |
Yes, I did this on purpose. As soon as you hit "Undo" the ShaderClipboard is cleared. The reason is that I can't be sure that the Undo operation doesn't delete the source brush, leaving an invalid reference in the Clipboard, which would crash DarkRadiant as soon as you try to paste the shader (from the now non-existent object). |
 |
The clipboard depends on the source brush existing in order to function? That sounds like a problem in itself. Let me try something... Okay, it didn't crash, but if I create two brushes, pick up the texture from the first, and then delete the first (certainly a normal operation bound to happen now and again while building areas), the clipboard texture is in fact lost. Shouldn't there just be a reference to the texture itself and not the brush, which would clear up both of these (admittedly minor) issues? |
|
|
Of course it doesn't crash, because I took care that the Clipboard is cleared on object deletion as well. ;) I chose to just store a reference, because I need more than just the shadername to perform the more complex projections/natural texture stuff. A patch has just its texture coords, whereas a brush has a so-called "TexDef", which is a matrix among a few other things. I didn't want to copy and store those data structures into the ShaderClipboard as the reference itself is sufficient. If you think that this is impractical, I can go the way of copying all those values into the clipboard as well. |
|
|
Not sure, kinda hard to decide. On the one hand, it was something that I thought (for quite some time now - I only just figured it out today) was an actual problem with selection or copy/paste. On the other hand, it's a relatively minor inconvenience to have the texture cleared (at least it doesn't crash). Perhaps we should suspend it (perhaps indefinitely). At least it'll be there if there's ever nothing else in the queue. |
|
|
This issue seems to be an annoyance, reopened and assigned to myself. |
- Anonymous
