I expect that New Connection will be assimilated by the FTP Browser window at the time when the Bookmarks window becomes a drawer, attached to it. The whole thing should meld together quite nicely.

Strangely enough, someone else commented roughly along the same lines just a day or two ago.

As I explained in my reply there, I have intentions of making improvements in these areas - for example, integrating the Bookmarks window into the FTP Browser window.

Just so you know, the 'Biohazzard' icon is actually Apple's Bonjour/Rendez Vous icon - if you had FTP servers available on your LAN then they would automaically show up in a list when you click the icon. It seems that you don't. This feature has become a standard feature of most FTP clients.

Thanks for the feedback!

Hi

I just tested this out with version 1.5.1 and it worked as expected.

If you have .DS_Store files on your server then Yummy might want to download them, but it should never upload them from your Mac if the "...and upload .DS_Store files" option is unchecked.

I can see that it might be more useful to have a checkbox which excludes .DS_Store completely (and maybe others such as Icon\r and .localized, for example)

At the moment, I suggest you add a filter to the server side to exclude .DS_Store files. Mail me if you need instructions for this.

-Jason

Good points. Although I'm sure the main source of confusion is the terminology - Transmit uses Favorites to store connection information and Yummy uses Bookmarks. Of course, Yummy has Favorites too but they are only for favorite folders - no connection details. For all those trying Yummy FTP after Transmit, it can be confusing...

I guess I could rename Bookmarks to Favorites, but then I'd have to rename Favorites to Shortcuts... and guess what? Fetch uses the term Shortcuts to describe saved connection details. Argh!

Just as well that I have plans to integrate the Bookmarks window into the FTP Browser window, which should make it quite a lot clearer.

What's happening, I suspect, is that your connection is over a firewall or NAT router which drops the connection automatically after a pre-determined amount of time without activity. Unfortunately, Yummy isn't notified that the connection has been terminated - the only way it knows is when a subsequent attempt to use the connection times out.

By default, Yummy's time out period is set to 2 minutes, so only waiting for 30 seconds will not allow Yummy enough time to recognize the connection loss and automatically reconnect - if you waited the full 2 minutes then it would reconnect as you expected. This value is set to 2 minutes for maximum compatibility reasons, however you may reduce the timeout value to 30 seconds if you wish by adjusting the 'Reconnect a connection if there is no activity for' slider in the Error Recovery tab of the Preferences. Once set, the dropped connection issue should no longer be a problem for you.

Let me know how it goes.

A new Mac software tracking site has been launched - It is called iusethis.com.

http://www.iusethis.com

Possibly the best way to describe iusethis.com is digg.com meets versiontracker. Users click the "I Use This" button and add their comments. There's many other interesting options too.

I'd really appreciate it if you were to click the "I Use This" button for Yummy FTP!

http://osx.iusethis.com/app/yummyftp

Thanks,
Jason

No, that NTP setting won't have any effect in this case, so that can't be it. I'll contact you off-line with a link to a test version of Yummy to try to pinpoint the problem.

Thanks for your patience

Sorry to hear you're having this problem. Yummy FTP checks whether the clock has been modified since you installed the trial, to counteract those attempting to reset the trial period. If this is detected then the trial ends almost immediately. The downside of this check is that if you have a defective battery in your Mac, or the clock was legitimately modified sufficiently then a false positive can be registered. Does this sounds like your situation?

Okie dokie

I'll check this out now I'm back. Thanks!

I'll check it out.

Ok, I'll look into that too

I'll take a look.

Thanks!! 

Is this an Intel Mac issue that nobody found? Out of all the beta testers I'd be really surprised if it's the case... but you never know.

Your only option is the Defaults button that you've already seen. This reverts everything to Factory Settings, which *should* mean that they are correct. Again, I can't test this out because I only have a PC here in the Internet cafe!! Let me know - if it's an Intel bug I'll fix it as soon as I return, which is this coming Thursday.

Thanks, and sorry for the trouble!!

-Jason

Thanks for the additional feedback