cocoaforge

Hello,
I was wondering about the invite window you get when you're sent a file.
Mine pops up in first ground, and its text zone ( where the name of the file is ) becomes active. I've often had the following problem :
When I'm chatting to someone and a file is sent, if I'm chatting, I'll accidently rename the file. But after that I can't figure out the proper extension and so, and therefore I usually cancel first send, and ask for a 2nd send.
Is it possible to have the pop up window to stay in back ground, say visible , but under the chat window ?

many thanks,

Yann

PS: I hope this isn't the nth time you're answering this question :S if it is I truly apologize on my poor search skills.

Hehe. It's come up several times before.

It's all changed in .8 (the next release) - there's a whole GUI for file transfers, it's very cool.

If you're feeling impatient, you could try the beta (see the stickied thread at the top of this forum) - but as it's a beta, some things aren't finished, it may have bugs that mess things up, etc. You know, the usual warnings that you get with beta software.

thanks a lot, I'm off to download it. even a beta on mac os can't be worse than my old windows pc

Everytime I get the invite to receive a file it shows up, but the file is never downloaded. I've tried several locations. No permission error. I can send a file without issues.

Any ideas?

gholland wrote:Everytime I get the invite to receive a file it shows up, but the file is never downloaded. I've tried several locations. No permission error. I can send a file without issues.

Any ideas?

Check your firewall/NAT?

Maybe check the ports that the file is being sent to and make sure that it's all flush?

Search around for more details on which ports to open. This has come up very recently in the Bugs forum, I recall.

gholland wrote:Everytime I get the invite to receive a file it shows up, but the file is never downloaded. I've tried several locations. No permission error. I can send a file without issues.

Any ideas?

this is your nat/firewall for sure! no doubts. i have the same exact problem with adium too. once i opened up port '1080' is starting working flawlessly i hope this helps.