View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000284||DarkRadiant||GUI||public||01.05.2007 14:55||17.06.2007 16:03|
|Fixed in Version||0.9.2|
|Summary||0000284: Update clipboard texture display in status bar upon Media tab selection|
|Description||Probably from the fix in 0000258:|
Selecting a texture in the Media tab now copies it into the clipboard (great). However, it does not update the clipboard texture listing (at least, that's what I think it is?) in the status bar at the bottom.
|Tags||No tags attached.|
Hm, this probably will need some redesign of the TextureBrowser/MediaBrowser behaviour, because selecting a shader in the MediaBrowser does not actually "load" the shader into the TextureBrowser.
The status text is referring to the shader in the TextureBrowser, not the one in the clipboard. It is probably the best to change the status bar to display the clipboard contents, not the TextureBrowser selection.
|I changed the status bar text to reflect the ShaderClipboard contents instead of the TextureBrowser selection.|
I might be misunderstanding this one, or there's still the original problem.
Start out with two walls, textureA and textureB. Also, the media tab contains a library of textureA..textureZ.
(1) If you MMB wall 1, textureA is loaded into the clipboard; that is, anything you ctrl-MMB will be painted as such, and the status bar shows, "ShaderClipboard: textureA"
(2) If you MMB wall 2, the same will happen, but with textureB.
(3) Now, if you go into the media tab (not texture tab) and LMB click textureC, you can now use ctrl-MMB to paint any surface with textureC. This would suggest that, similar to (1) above, textureC is now in the ShaderClipboard, is it not? Don't get me wrong, this is a great feature! The only question being raised here is that the ShaderClipboard texture in the statusbar still indicates:
So, even though my LMB click in Media changed my paintbrush to be textureC, the statusbar doesn't tell me. Know what I mean?
Edit: Let me re-emphasize though, this is very minor. If it means breaking any other behavior or loss of performance, it's not worth addressing.
|Fixed in SVN.|
|01.05.2007 14:55||SneaksieDave||New Issue|
|01.05.2007 17:13||greebo||Note Added: 0000605|
|01.05.2007 17:13||greebo||Status||new => confirmed|
|01.05.2007 17:13||greebo||Status||confirmed => assigned|
|01.05.2007 17:13||greebo||Assigned To||=> greebo|
|01.05.2007 19:16||greebo||Status||assigned => resolved|
|01.05.2007 19:16||greebo||Fixed in Version||=> latest SVN|
|01.05.2007 19:16||greebo||Resolution||open => fixed|
|01.05.2007 19:16||greebo||Note Added: 0000610|
|15.06.2007 21:25||SneaksieDave||Status||resolved => feedback|
|15.06.2007 21:25||SneaksieDave||Resolution||fixed => reopened|
|15.06.2007 21:25||SneaksieDave||Note Added: 0000684|
|16.06.2007 02:47||SneaksieDave||Note Edited: 0000684|
|16.06.2007 06:16||greebo||Status||feedback => assigned|
|16.06.2007 06:27||greebo||Status||assigned => resolved|
|16.06.2007 06:27||greebo||Fixed in Version||0.9.1 => latest SVN|
|16.06.2007 06:27||greebo||Resolution||reopened => fixed|
|16.06.2007 06:27||greebo||Note Added: 0000689|
|17.06.2007 16:03||SneaksieDave||Status||resolved => closed|