Friday, April 01, 2005

Build 385 Interruptus 

There was a glitch in the uploading of Foxfire! 8.0 Build 385 late yesterday. If you downloaded the full install, please download the partial setup to get properly updated.

If you only downloaded the partial install, please re-download it again.

Otherwise, you will receive a beta expiration notice.

Comment

Thursday, March 31, 2005

Foxfire! 8.0 - Build 385 

Build 385 is available in both Full and Partial installs.

Only a few major fixes in here due to some bad data.

1. More fixes on indexing that hopefully have now cleared up. (Thanks Mike for the reports)

2. Fix on the Export that was caused when exporting requests that were not in their own folder.

3. Fix for the Join Tree not showing up properly in preferences with a large number of relationships.


FF! 8.0 Development Blog

Comment

Wednesday, March 30, 2005

Sample Data Problem 

There is a problem with some of the sample data used in the full install of Foxfire! 8.0 build 384. A new update will be posted shortly.


Comment

Tuesday, March 29, 2005

Foxfire! 8.0 - Build 384 Now Available 

Full Install (Recommended)
Partial Install

Quite a bit of plumbing changes in this release, including cosmetic terminology changes. Here's a quick summary:

Request Manager. A variety of fixes for exporting and importing, including the ability to import and export the request folder between users.

Data Item Picker. Label editor has been fixed so it supports spacing and custom fields much better. When you create a new data item, it automatically sorts the list correctly.

Filter Tab. When you're modifying a filter value directly in the work bench, we've now turned on the Confirmation setting so users have to hit Enter to move to the next field. This should help resolve a number of confusing editing behaviors that have been reported.

Sort/Group. We no longer allow sorting by Memo fields, primarily to make it easier to work with.

And a variety of changes in the Preference Editor and overall functionality reducing crashes and making it easier to report problems.

As always, please shoot over bugs and issues directly to support@micromegasystems.com.

Thanks

Comment

This page is powered by Blogger. Isn't yours?