Page 1 of 1

NeoBookFM/FTP v1.1 Update Released

PostPosted: Thu Sep 02, 2010 12:01 pm
by Neosoft Support
NeoSoft Corp. has released NeoBookFM/FTP version 1.1. This update can be downloaded from:

http://www.neosoftware.com/neobook/modules/plugins/singlefile.php?cid=12&lid=131

This update contains the following:

Enhancements

• Added a ShowFiles property to the fmSetFileBrowserProperties action. This will allow the file browser to display only the tree view if desired.

• Decreased the amount of time required to display the first created local file browser. Previously, generating a list of files could be slow the first time FM/FTP was used after starting Windows. This was a result of FM/FTP being forced to wait while Windows generated its icon cache. FM/FTP now displays the file browser immediately while Windows generates icons in the background.

Fixes

• Corrected compatibility issues that occurred when connecting to servers running PureFTP software.

• Fixed a problem that could cause a noticeable delay when shutting down a publication using FM/FTP. On some older Windows configurations this could also result in a thread resource being left in memory. (This only affected a very small number of systems.)

• Corrected a problem that prevented the cancellation of a file transfer when copying large folders to or from a remote connection.
And several other minor fixes.

PostPosted: Thu Sep 02, 2010 5:15 pm
by Scherzkeks
Added a ShowFiles property to the fmSetFileBrowserProperties action. This will allow the file browser to display only the tree view if desired.


Nice one, thank you!

The Tree is not ordered with C, D, E... instead ordered A-Z from Drive names. Is there a Option to change this? or is this a Bug?
The previous Version is working like expected.

Cheers

PostPosted: Fri Sep 03, 2010 10:05 am
by Neosoft Support
The Tree is not ordered with C, D, E... instead ordered A-Z from Drive names. Is there a Option to change this? or is this a Bug?
The previous Version is working like expected.


You're right - it's a bug. We'll release a fix as soon as possible.