Update of bug #35380 (project gnustep):
Status: Duplicate => Need Info
Open/Closed: Closed => In Test
_______________________________________________________
Follow-up Comment #4:
Ok, so I had to dig a little deeper. It turns out that somewhere further than
I imagined in our code we actually intentionally disable the NSImageView when
we first load it. The comment being "Disabling Image View prevents it from
being tabbed to"; I guess that was important when we first put this in.
Interestingly however on Mac OS X, that does NOT cause a greying out of the
Image itself (just of the border rectangle). I've attached a 2.X NIB to run
on Mac OS X (10.6.8 for me). If you just run it in interface test mode it
uses bindings to let you enable and disable the NSImageView, you can let me
know what you see.
I don't especially care, but it seems that Cocoa doesn't grey the image.
Unless I'm missing something (and I often am).
So, I've reopened the bug pending your decision of how you _want_ it to
behave.
(file #24933)
_______________________________________________________
Additional Item Attachment:
File name: EnableNSImageTest.nib.zip Size:5 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?35380>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gnustep
