I wrote this simple application as a test for some concepts as I was experimenting with Rhapsody. I wanted to test the ability of NSImage to handle JPG and GIF images, and experiment with NSOutlineView.
- It seems to me that sometimes either NSImage or NSImage view are causing crashing type signals, but they are not raising errors! From GDB
(gdb) run
Program received signal SIGABRT, Aborted.
0x5039e5c in kill ()
I have included a GIF that seems to cause the error to repeat (annotatedPW.gif), but I have also had the file display without error???, only to crash when the window resizes. I have another application that displays singular images (like OmniImageView.app), that uses my own image view class, and it does not have any trouble with this image. YMMV, comments welcome!
- For fun I have the up and down arrows attached to menu items, I could have caught the key down as part of the window event, but this seemed easier (that's the point right?). Anyway, on my Intel machine this results in a double message (move up/down 2 images instead of one). I had the delete image menu item set to the DEL key, but it was deleting 2 images ...
- the outline view works pretty much as expected, however I consistently get exceptions when I try to change the tree of objects. For example, if I delete an image, I should reload the parent, .. right? I have tried removing the tree node before and after removing the file, before and after calling "[outlineView reloadItem:parent]". If anyone can correct this please send me the changes, I am tired of fighting with it.
- replace the image view with a switch view, then flip in the correct view type for the file selected (text, rtf, m/h/c, ...). Possibly do this with bundles so additional file formats can be easily added. Not of any real practical value, but would be an interesting exercise in bundle design.
- replace the image view with a thumbnail matrix, so when you select a directory all the images in that directory display as thumbnails.
- have the up/down keys scan down the outline view to the next valid image. (might be one row, might be 200)
- add a 'Find' panel to search for an image by name (size? directory?)
