I'm using this now, but I'd like it better if it had these features:
hey, thank you for adding the "move to" shortcuts! very appreciated
the beta seems to work very nicely(ppc)
3 things:
-a "crop" button in the toolbar is needed
-in the like keyboard configuration window within preferences the x apparently does nothing at all. also, to change the key combinationits it is awkward to have make a whole new button and delete the old one you should be able to change a key combo in one step.
-movie placeholders (its alright if its not gonna happen. would be very cool though)
thank you very very much
> a "crop" button in the toolbar is needed
Yes.
> in the like keyboard configuration window within preferences the x apparently does nothing at all.
It should restore the shortcut to defaults. I guess it should be disabled if they are already set to the defaults.
> also, to change the key combinationits it is awkward to have make a whole new button and delete the old one you should be able to change a key combo in one step.
Granted, but I am not sure what to do instead - I don't think it's very friendly to make other keyboard shortcuts disappear silently, either. As it is now, you can at least drag the old one to the new action.
> movie placeholders (its alright if its not gonna happen. would be very cool though)
Theoretically, I could even make movies PLAY in Xee without too much effort, but that's definitely feature bloat. Not sure what I'll do about this.
EXCELENT PROGRAM!!!, congrats!!! The best image brouser for MAC. Im using macbook dual core 2, and the only bug i find is when i rotate the image and save it (without recompression) it saves the file replacing the old one but the program after doing that crashes and closes. I dont know why. Also the ^save lossessly^option in the menu appears in grey, maybe im doing something wrong.
I use in windows xp irfanview and the only thing i miss is that u can edit the image gamma, histogram, contrast...
Good job on the cropping tool!!!
Date/Time: 2006-12-26 13:51:19.568 -0600
OS Version: 10.4.8 (Build 8N1106)
Report Version: 4
Command: Xee
Path: /Applications/Multimedia/Xee.app/Contents/MacOS/Xee
Parent: WindowServer [52]
Version: ??? (2.0 beta 1)
PID: 1715
Thread: 1
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x65426c6c
Thread 0:
0 libSystem.B.dylib 0x90009857 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082b2f3 CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x9082ab0e CFRunLoopRunInMode + 61
3 com.apple.HIToolbox 0x92ddabef RunCurrentEventLoopInMode + 285
4 com.apple.HIToolbox 0x92dda2fd ReceiveNextEventCommon + 385
5 com.apple.HIToolbox 0x92dda154 BlockUntilNextEventMatchingListInMode + 81
6 com.apple.AppKit 0x9325f465 _DPSNextEvent + 572
7 com.apple.AppKit 0x9325f056 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
8 com.apple.AppKit 0x93258ddb -[NSApplication run] + 512
9 com.apple.AppKit 0x9324cd2f NSApplicationMain + 573
10 cx.c3.xee 0x00002292 _start + 216
11 cx.c3.xee 0x000021b9 start + 41
Thread 1 Crashed:
0 libobjc.A.dylib 0x90a564c7 objc_msgSend + 23
1 com.apple.Foundation 0x925f836c forkThreadForFunction + 123
2 libSystem.B.dylib 0x90023d87 _pthread_body + 84
Thread 2:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 com.apple.Foundation 0x9264e2f8 -[NSConditionLock lockWhenCondition:] + 39
2 com.apple.AppKit 0x93336270 -[NSUIHeartBeat _heartBeatThread:] + 377
3 com.apple.Foundation 0x925f836c forkThreadForFunction + 123
4 libSystem.B.dylib 0x90023d87 _pthread_body + 84
Thread 3:
0 libSystem.B.dylib 0x90009857 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082b2f3 CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x9082ab0e CFRunLoopRunInMode + 61
3 com.apple.audio.CoreAudio 0x9146541e HALRunLoop::OwnThread(void*) + 158
4 com.apple.audio.CoreAudio 0x91465239 CAPThread::Entry(CAPThread*) + 93
5 libSystem.B.dylib 0x90023d87 _pthread_body + 84
Thread 4:
0 libSystem.B.dylib 0x900268bc kevent + 12
1 ...ple.CoreServices.CarbonCore 0x90cb5f84 PrivateMPEntryPoint + 51
2 libSystem.B.dylib 0x90023d87 _pthread_body + 84
Thread 5:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 ...ple.CoreServices.CarbonCore 0x90cb6129 MPWaitOnQueue + 198
2 com.apple.DesktopServices 0x9251e943 TNodeSyncTask::SyncTaskProc(void*) + 143
3 ...ple.CoreServices.CarbonCore 0x90cb5f84 PrivateMPEntryPoint + 51
4 libSystem.B.dylib 0x90023d87 _pthread_body + 84
Thread 1 crashed with X86 Thread State (32-bit):
eax: 0x65426c6c ebx: 0xb009ded4 ecx: 0x00081d40 edx: 0x900268bc
edi: 0x65426c74 esi: 0x003ad920 ebp: 0xb009df08 esp: 0xb009dea4
ss: 0x0000001f efl: 0x00010206 eip: 0x90a564c7 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
The "Save losslessly" option isn't properly implemented yet, so that's why it's grey. I'll have a look at that crash, though. Thanks!
Xee turns out to be the easiest to use image viewer for my 59 year old mother, who is using her iBook for 1 month now.
So great work!
But we had a problem this day. She has a lot of picture-CDs of her friends. When watching them, there's often the need to rotate an image. This is not possible with Xee. When the volume is write-protected you get an error-message.
It's also not possible to rotate non-jpeg images.
Is there a particular philosophy behind these two points or are you working on implementing these functionalities?
Me again!
Found your 2.0beta1. Both of my mentionned points in post #406 are already implemented. Great!!
One additional little point:
Pictures should be resized to window (or screen in fullscreen) after rotation.
>>406
You say "She has a lot of picture-CDs of her friends. When watching them, there's often the need to rotate an image. This is not possible with Xee. When the volume is write-protected you get an error-message."
You can't change something that is read-only, such as a CD-ROM or CD-R! I don't see how this could be now "already implemented". Unless you save some sort of cached metadata.
>>408 I don't think he's trying to save the rotation, just rotate temporarily, and that was what was failing before.
> Theoretically, I could even make movies PLAY in Xee without too much effort, but that's definitely feature bloat. Not sure what I'll do about this.
Please don't. If would make sense if Xee offered a directory view with thumbnail previews but as it is right now, Xee is an image browser. There are other programs to let you preview/view a batch of movies sequentially.
Any way to turn off the delete confirmation box when clicking the Delete button on the toolbar?
For some reason with this build, I have an odd problem with viewing large amounts of images on a network share. I cannot reproduce this on local directories. It's a bit difficult to explain but here goes.
Say I go through a directory with more than a hundred or so images, all rather large (think manga) and then I use finder to go to a different directory and double-click an image to open it in Xee. Sometimes a problem will occur where Xee will resize itself to the dimensions of the image but will display nothing but black. When Xee is like this, I can't navigate to other images either.
Trying to open another image through the finder will only get another all-black image. Trying to bring up the open dialogue inside Xee will just cause it to eat up CPU. Here's the sample log on Xee when it's in that locked-up state:
Analysis of sampling pid 2429 every 10.000000 milliseconds
Call graph:
300 Thread_0f07
300 start
300 _start
300 NSApplicationMain
300 -[NSApplication run]
300 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
300 _DPSNextEvent
300 _NSHandleCarbonMenuEvent
300 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:]
300 -[NSMenu performActionForItemAtIndex:]
300 -[NSApplication sendAction:to:from:]
300 -[XeeDelegate openDocument:]
300 -[NSSavePanel(NSSavePanelRuntime) runModalForTypes:]
300 -[NSSavePanel(NSSavePanelRuntime) runModalForDirectory:file:types:]
300 -[NSApplication runModalForWindow:]
300 -[NSApplication beginModalSessionForWindow:]
300 -[NSApplication _commonBeginModalSessionForWindow:relativeToWindow:modalDelegate:didEndSelector:contextInfo:]
300 -[NSApplication _orderFrontModalWindow:relativeToWindow:]
300 -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:]
300 -[NSWindow _commonAwake]
300 -[NSWindow(NSDrag) _registerDragTypesIfNeeded]
300 -[NSWindow(NSDrag) _registerDragTypes:]
300 -[NSView(NSDrag) _addDragTypesTo:]
300 objc_msgSend
300 objc_msgSend
300 Thread_1003
300 _pthread_body
300 __ape_agent
300 mach_msg_trap
300 mach_msg_trap
300 Thread_1103
300 _pthread_body
300 forkThreadForFunction
300 kevent
300 keventTotal number in stack (recursive counted multiple, when >=5):Sort by top of stack, same collapsed (when >= 5):
kevent 300
mach_msg_trap 300
objc_msgSend 300
Sample analysis of process 2429 written to file /dev/stdout
Sampling process 2429 each 10 msecs 300 timesIntel Mac mini on 10.4.8
WAHa,
this a great little app. Needed something that would flip thru photos. u did good though I haven't tested it throughly.
ohh, does need one thing. Using the X button really should close the app program unless another is open.
>>414
No. That's not how Mac apps work.
At least, that's not how they should work, according to the HIG.
I've been trying, but I can't reproduce this. Can you figure out a solid way to reproduce it? Also, what kind of network share?
>>416
I can't reproduce it consistently in the sense that I can't figure out why if I view one set of images in one directory, I can trigger the problem always but if I go through another directory of a similar number of images, it won't trigger. But for known 'bad' directories, I can definitely reproduce the bug consistently.
It's a CIFS share off a Win2K3 server. I can confirm that I had no problems using the stable version of Xee and did not recall any problem using the early Intel betas either.
>>416
On a side note, can I again make a request for AppleScripting support?
Does opening an image in a directory, and then clicking another image there (to re-use the same window), and then doing stuff cause the problem? Because I've found and fixed a bug relating to that already.
Also, I want AppleScripting too but it won't be in 2.0, I'm trying to polish that off and release it now without adding anything new. Also if somebody with more experience with AppleScript than me wants to help me out with it, that would be appreciated because I don't have much of a clue how it should be done.
>>419
Doesn't seem to trigger it in that case. This bug is actually bugging me a lot because it essentially all my manga are stored on a network share so I run into this pretty much every other volume of reading. If you want me to run a special build that outputs lots and lots of output and debug messages, I'm up for it as long as it helps.
o key bindings doesn't seem to stay; after a restart they are either gone or have multipled (tested on G4 only); e.g. setting "L" to loop, after a restart you can find "L" several times in the list
o maybe the default OSX print dialog would be nice; I know it's a viewer but sometimes for quick printing...
nice work anyway
this one: http://wakaba.c3.cx/releases/mac/Xee2.0beta1.zip
problem exists even with a clean cx.c3.xee.plist
It also occurs with a "clean" account (in this case root which isn't spoiled by any customizations); The "L" is funny as it really gets multiplied; I set horizontal and vertical mirror to "H" and "V", which are kept after a restart of the programm but doesn't work
I haven't tested it yet on intel mac
All right, I see the problem. I'll try to get it fixed. Thanks!
All right, I think I've finally got all the GUI tweaks in, and everything should now work! I also fixed most of the reported bugs, except for the network share one which I haven't gotten around to reproducing yet. Hopefully, though, the program should be nearly ready for release now, except for translations, which I'm going to try and get arranged now, at least for Japanese.
So! If you don't report bugs now, they won't get fixed in the final version!
for some reason the Xee2.0 beta2 is still significantly slower on my old PB G4 1.25 Ghz than Xee 1.21 while loading larger JPEG images (both versions set to YUV). While 1.21 loads them almost instantaneously, 2.0b2 seems to need more memory. hope this is not related to the universal binary...
I really like Xee and I have two suggestions:
Thank you and keep up the good work!
That is still strange, because most of my own tests suggest it should be about as fast or a little faster. I could add a hidden option to turn off the progressive display, in case that is causing trouble on some old graphics chip...
It's not really a select tool and more just a crop tool, so I dunno. You can always just apply the cropping and then copy. Also, just press cmd-V to make a new image from the clipboard.
The scrollbars, I dunno. Not only is the standard scrollbar code on OS X pretty buggy, it'd also most likely be slower at scrolling if it had to draw the scrollbars too, and they'd clutter up the interface. Normally you would expect them, but ACDSee, which I am copying to a large extent, doesn't have them either.
Xee2.0beta2 fixes the problem with Cmd-0 I was experiencing with 2.0beta1, but now I can't open Help > Keyboard Shortcuts... The menu item simply flashes and goes away, as it should... And, that's it. Nothing else comes up. It doesn't display Keyboard Shortcuts. I tried deleting cx.c3.xee.plist, but that didn't resolve the problem. Thanks again.
Hmm, it works fine here. Can you open the preferences normally?
I just discovered this. I opened it up through Preferences (which, to answer your question, works fine). Then, I went back to Help > Keyboard Shortcuts (KS) and now it works. But, if I quit Xee and go to Help > KS it's back to square one; it doesn't open. But, it will if I open it through Preferences first, again. Looks like a simple bug.
Oh! I get it, it IS a very simple bug. Thanks for catching that.
>>425
My problem with the network shares still persists in this version but here's some more info.
When my problem occurs, the status bar will say "Cannot display image" and the window/canvas will be black. Using the file open dialogue inside Xee will crash. In the previous beta, Xee would just drive up CPU utilisation.
Here's the crash log in case it helps:
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000020Thread 0 Crashed:
0 libobjc.A.dylib 0x90a54380 objc_msgSend + 16
1 com.apple.AppKit 0x9335c070 -[NSView(NSDrag) _addDragTypesTo:] + 55
2 com.apple.AppKit 0x9335bec6 -[NSWindow(NSDrag) _registerDragTypes:] + 120
3 com.apple.AppKit 0x932e8e6f -[NSWindow(NSDrag) _registerDragTypesIfNeeded] + 66
4 com.apple.AppKit 0x932e79ef -[NSWindow _commonAwake] + 2575
5 com.apple.AppKit 0x932900af -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 512
6 com.apple.AppKit 0x93339854 -[NSApplication _orderFrontModalWindow:relativeToWindow:] + 686
7 com.apple.AppKit 0x9333933a -[NSApplication _commonBeginModalSessionForWindow:relativeToWindow:modalDelegate:didEndSelector:contextInfo:] + 678
8 com.apple.AppKit 0x9333908e -[NSApplication beginModalSessionForWindow:] + 72
9 com.apple.AppKit 0x93338f6d -[NSApplication runModalForWindow:] + 109
10 com.apple.AppKit 0x9345ee20 -[NSSavePanel(NSSavePanelRuntime) runModalForDirectory:file:types:] + 218
11 com.apple.AppKit 0x9345ec31 -[NSSavePanel(NSSavePanelRuntime) runModalForTypes:] + 71
12 cx.c3.xee 0x0000c522 -[XeeDelegate openDocument:] + 188
13 com.apple.AppKit 0x9335cd88 -[NSApplication sendAction:to:from:] + 107
14 com.apple.AppKit 0x9340ace7 -[NSMenu performActionForItemAtIndex:] + 455
15 com.apple.AppKit 0x9340aa29 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 103
16 com.apple.AppKit 0x9333be16 _NSHandleCarbonMenuEvent + 477
17 com.apple.AppKit 0x9326f7fc _DPSNextEvent + 1491
18 com.apple.AppKit 0x9326f056 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
19 com.apple.AppKit 0x93268ddb -[NSApplication run] + 512
20 com.apple.AppKit 0x9325cd2f NSApplicationMain + 573
21 cx.c3.xee 0x00002db2 _start + 216
22 cx.c3.xee 0x00002cd9 start + 41Thread 1:
0 libSystem.B.dylib 0x90009857 mach_msg_trap + 7
1 com.unsanity.ape 0xc0001cac __ape_agent + 307
2 libSystem.B.dylib 0x90023d87 _pthread_body + 84Thread 2:
0 libSystem.B.dylib 0x900268bc kevent + 12
1 com.apple.Foundation 0x925f536c forkThreadForFunction + 123
2 libSystem.B.dylib 0x90023d87 _pthread_body + 84Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x925f0f26 ecx: 0x90a65c00 edx: 0x16a8f650
edi: 0x00000004 esi: 0x00000000 ebp: 0xbffff0b8 esp: 0xbfffee58
ss: 0x0000001f efl: 0x00210202 eip: 0x90a54380 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037I just tried disabling all my APE extensions but I can still crash Xee using the same steps. Though, the crash log is much shorter:
Command: Xee
Path: /Applications/Xee.app/Contents/MacOS/Xee
Parent: WindowServer [60]
Version: ??? (2.0 beta 2)
PID: 3776
Thread: Unknown
Link (dyld) error:
image not foundWow, that is a weird crash. Something is definitely fucked up there.
Open Console.app (in /Applications/Utilities/) and see if it says anything?
That's a really weird error though. I don't think anything involved uses weak linking or bundles.
When my problem occurs:
2007-01-19 18:48:12.849 Xee[5180] *** -[NSBundle load]: Couldn't dynamically load framework codeWhen I crash Xee:
2007-01-19 18:49:15.549 Xee[5180] unable to load nib data: /System/Library/Frameworks/AppKit.framework/Resources/English.lproj/NSNavPanelContentView.nib
2007-01-19 18:49:15.550 Xee[5180] unable to load nib data: /System/Library/Frameworks/AppKit.framework/Resources/English.lproj/NSNavView.nibAre you trying to open an image, or an archive, when this happens?
Image in a directory different from the directory the image resides in.
Many thanx 4 this great app, just what we needed for osX !
This image viewer would replace Preview right away if only it could open .pdf and - even better - .ps
the old version 1.21 kept the settings for an image once applied (i.e. rotating 90 degree, jpeg), I assume by writing the exiftags. This is no longer possible with 2.0 beta 2.
I hope I didn't miss some obvious settings...
I finally managed to set up an SMB share to test this on, and I do see the problem.
It smells just a little bit like samba itself being very buggy, though. If that's the case, I can try and work around it but I can't guarantee I will have much success.
(For fun, try this: delete the picture you're viewing from inside Xee. Then browse forward a couple of images and then back to the deleted image. For me, it's still there and can be loaded, although it's disappeared from the Finder!)
I feel vindicated that it's not some imaginary problem only I can reproduce. But now that you mention it, I do have odd problems like this with Window shares in general. Though it also seems like that the problem occurs less if I don't browse all the way to the last image of a directory before opening an image from another directory.
I found the bug, and fixed it! However, the basic problem is that the kqueue functions that Xee uses to monitor changes in the filesystem (even when it does things like delete an image itself) don't work on SMB shares. So behaviour will always be a bit broken on SMB, but at least browsing works right now.
(Turns out the trigger for the bug is simply viewing enough images on an SMB share. Just opening one and holding down the skip-to-next button will trigger it after a while.)
Could you pretty please not write the name of every file to the console log?
That's what you get for running beta versions! It'll be removed in the final.
Hi,
I started using Xee some days ago, I would like to have two more options:
Great software!
Both options exist in the 2.0 beta already, the first in the advanced prefs, and the second in the View menu.
In 1.2.1 Xee would stay fixed to a certain area of the screen when opening a new window. Now it opens windows in the upper left. Is there any chance that Xee might be able to regain this little bit of functionality?
Well, it's finally time to release this, I think!
http://wakaba.c3.cx/releases/mac/Xee2.0.zip
http://wakaba.c3.cx/releases/mac/Xee2.0_src.zip
http://wakaba.c3.cx/s/apps/xee.html
I've tried to list the changes on the Xee homepage, but I'm not sure I can even remember them all any longer!
Also, sorry, >>453, you were a bit too late. I'll look into that for the next version.
I just saw that the new version ought to open archive files (with help of the unarchiver).
Ho can i use this feature? Whenever i open a zip (or cbz) in Xee (either by File>Open or by dropping the zip at the program icon) Xee states to be unable to display the file, though the unarchiver is perfectly able to open and extract the archive...
If you upgraded The Unarchiver and put the old version in the trash, try emptying the trash and see if that helps.
I'd prefer that Xee 2.0 doesn't associate itself with my archives.
I don't want browse archived images and prefer to extract big binaries with stuffit instead of Xee (which doesn't work at all neither with the Unarchiver nor without).
Unfortunately not. I emptied my trash, loged out/in again without changes. Even creating a new zip (by using the Finder) I'm not able to watch the content in Xee.
Is there a way to determine whether or not Xee has found The Unarchiver?
Have a look at the Xee Preferences. There's a panel named Formats, uncheck the last two items and Xee wont open your archives anymore.
I'd also like to print my images from Xee.
Actually, it doesn't associate itself with anything by default. If it does, it's OS X that picked that association by itself.
If it doesn't find it, it opens a dialog to tell you. With this particular bug, it finds it, but somehow can't load the code from it. Check Console.app for any messages.
For now, this is outside the scope of the app. If I implemented printing, I'd like to do it properly, but I don't really have the time to work on it.
I'd be happy to accept any submitted code for this, though.
Furhtermore, try deleting both Xee and The Unarchiver, emptying the trash, and installing them again. I really wish I could give some more useful advice, but while I had the same problem at one point during development, it pretty much went away on its own, and I really don't know why.
I tried deleting both Xee and The Unarchiver and the problem of not viewing inside archives if still persists.
Could you post the previous versions (The Unarchiver 1.3 and Xee 2.0 Beta2) again?
I know that this combination worked before, so maybe it'll narrrow down the problem. Thanks!
They should be in http://wakaba.c3.cx/releases/mac/old/
>> 461
>> 462
Still not working :(. I tested the following: removed both Xee and The Unarchiver and installed Xee alone (to make sure Xee will definitely find nothing else). After the box you mentioned poped up I installed The Unarchiver and tried again - the box did not appear though Xee wasn't able to open the archives. However Console.app did not show any error message at all :(.
I'd like to give you some better failure descriptions, unfortunately I don't have Xcode/Objective C experience (I assume python knowledge doesn't help at this point... :( ).
Come to think of it, I know one other trick that might work, but it will not explain what was actually wrong: You could try doing "Show package contents" on both Xee and The Unarchiver, and then copying the Frameworks folder over to Xee, which should let it use those frameworks without having to load them from The Unarchiver.
Yes, that finally did the trick.
It seems the framework could not be (cross)loaded from The Unarchiver. If you compile a version with debug output around the framework loading point (I normally use something like "ive found the path here, im using that path there" when i'm to lazy to use a debugger), post the link to the zip and I will verify this.
And/Or giving me some pointers to some good Xcode/ObjC introduction/tutorial for regaled python/java/xslt programmers would be even better - so I could get my hands dirty without whining next time something breaks... ;)
I haven't tried the copying over the frameworks solution yet, but I found that:
Xee 2.0 + The Unarchiver 1.3 works.
Xee 2.0 + The Unarchiver 1.4 does not work.
I repeated it several times, emptying the trash every time, so it seems that it cannot load the frameworks from the 1.4 package for some reason.
That's funny. It works fine on my main machine, but with a fresh install on my secondary machine, it fails in the same way. Some research reveals that it finds the framework just fine, but fails to load it, giving no reason. This will be somewhat tricky to figure out.
>>469 and >>470, what machines are you doing this on? It works on Intel for me, but not on PPC.
it doesnt load archives from the unarchiver on my PPC
the archives unarchive fine with the unarchiver otherwise
console doesnt say anything, xee says "Couldnt display file"
That's weird...
I'm on an Intel machine...MacBook Core Duo to be specific...
I had the same problem and copying the Frameworks folder over worked like a charm. And, for the record, I have an MBP 2 GHz Core Duo.
Read the earlier posts.
hey, great thing. but could you add a possibility to enter a numeric zoom level (in the toolbar or in the status bar)? and add maybe shortcuts for 25%, 50%, 200%? that would be nice.
Hi,
I like Xee very much, great work!
only thing i'm missing, while crop, it would be nice,
to see position infos in status bar.
i used irfanview (on windows) and this was one of
major features i loved...
regards, stefan
Hi,
I like Xee very much, great work!
only thing i'm missing, while crop, it would be nice,
to see position infos in status bar.
i used irfanview (on windows) and this was one of
major features i loved...
regards, stefan
Just wanted to say: absolutely great program !
I'll post this in here too, because it's mostly Xee-related anyway:
http://wakaba.c3.cx/releases/mac/TheUnarchiver1.5.zip
This version should hopefully fix the problems with loading archives! Anybody who had the problems, if you want to confirm that it has been fixed, install this and re-install Xee (or just delete the Frameworks folder from it if you copied it oveer)!
(ppc) xee 2.0 works with the unarchiver again
nice, thankyou.
Great tool! Any plans for scripting? I often do slideshows full of photos, and haven't found a lightweight way to organize them in a hurry. If I could feed your program a simple text document listing image filenames, along with a few display options, it would out-do OpenOffice's Presentation tool, and Apple's iPhoto. Display options would include custom timings on each slide, including wait until manual advance on any given slide, and perhaps simple captions.
That fixed the problem. Thanks for a great couple of programs.
Further note on scripting... it would be great to have 2 (or more?) threads (or just groups) of photos in the slideshow. One thread would cycle slides continuously. Hit some key, first thread stops, and a manual thread begins. People could watch slides from my travels flip by as I talk about the trip generally, and then when I want to discuss a particular photo, I'd jump to the thread of photos that deserve some explanation. Finish the explanation, then hit some key, and back to the first thread. Doable?
Well, that's sounding like a whole app in its own right already. I'm doing my best to avoid feature creep, and this seems a pretty niche feature, so I don't really see it as something worth putting much effort into.
Hi!
I think it would be great to choose in the preference panel if the images will be saved automatically when rotated or not! I miss this option and when saving in version 2.0 with command-s - the thumbnails of the images are not rotated :((((((( Or is there an option to set?
That's probably just the Finder being buggy. Xee does rotate the thumbnails when you save images. Or alternatively your camera saves thumbnails in some weird format that Xee doesn't support?
If only Xee had a Print button I could add on the toolbar... :) I need to print through Preview to do that
You can at least set Preview as the default editor, and press Command-E.
Hi,
I have to say that this is the best Image viewer for OS X. I switched from windows where I was used to Xnview. I work everyday with BBEdit and I would like to have button in the bar that will copy image information and create this line: image.jpg" width="100" height="100" and put it into clipboard. This function will let me browse hundreds prepared images for the web and just copy the information for the HTML image tag.
Also Autodesk Maya IFF format will be nice.
thank you for this great application.
P.S. sorry about my english
2.0 has a Maya IFF loader, but it is not extensively tested because I don't have very many test cases. If you have any files that do not work, send them to me.
Hello, Mr. Ã gren.
First off, I do need to say this (though you probably have heard it a thousand times before):
This is one of the best image viewing applications for Mac I've ever used.
When I first started to use Mac OS X, I realized that for my image viewing needs, Preview quite frankly won't cut it.
What was I supposed to do?
Open pictures one at a time? (double-click, close, double-click, close, etc.)
Or perhaps "Select all" in Finder, then open them, then use the drawer thing to browse, etc. etc. etc.
Why must it be so complicated??
So I then desperately sought out a good image viewer.
I think I downloaded and tried out 4-5 of them.
Some were not too bad, or "partially satisfactory", but still, not good enough for permanent use.
Then, through a forum, I found Xee, and boy, was it a godsend.
After trying it out, I KNEW it was THE image viewer for the Mac.
It is not only well-made, but also highly customizable.
(And the way you customize the keyboard shortcuts is really awesome: [+] [-] drag-and-drop...
In my opinion, ALL apps should allow you to do this.)
Okay, enough gratuitous praise. =P
I have a suggestion. (of course)
I noticed that if I resize the window (or Zoom it), then close it,
the next time a Xee window is opened, it does not retain that size.
I do not know if this was done on purpose,
but personally, I like my programs to retain window sizes. (and I'm sure a lot of other people like this too)
It would be great if you could either:
-make "retain the window size" the default behavior
or
-add a Preference to retain the window size
Thanks a lot for your time!
And of course, keep up the great work!! :)
-Xee user