We’ve had some reports of at least two different bugs that were affecting image viewing and image saving. Both were rare, ugly, and could involve data loss. More importantly, they’ve both been fixed in Stacks 1.1.4. Even though these bugs were rare, we’re recommending that you update as soon as possible even if you were never affected by these bugs.

Stacks: Get it Now

Just the bugs

Four separate changes were made, but they all involved these bugs. We’ve also added more detailed error reporting if bugs like this should crop up again. No other changes to Stacks functionality were made.

Requirements

You must have RapidWeaver 4.2.1 or newer to use Stacks. Although we strongly encourage people to use the latest version of RapidWeaver at all times. Please double check to make sure you're not still running RapidWeaver 4.2(.0). And see this post for more details: Update RapidWeaver!

How much?

Stacks is $19.95, but you can try the demo for free. The demo has all the features, but just limits the number of items on the page.

How do I install it?

The easiest way to install it is to:

1. Open RapidWeaver
2. Close any open documents.
3. Download the Stacks disk image.
4. Double click on the Stacks plugin in the disk image window.
5. Quit and restart RapidWeaver

It looks like we missed one more bug. It wasn't experienced by many, but it looks like the HUD Framework we were using was doing something a bit strange to the Core Image library. The color well controls were doing something very odd and on some graphics cards leaving things in a state where the other Core Image operations were being affected. We've replaced the color wells. They don't look quite a sleek now -- but form follows function -- and at least they don't cause any problems.

For more details on the features and fixes we made in big Stacks 1.1, check out the big list.

Stacks: Get it Now

With all the optimizations we made to image handling and memory allocation in Stacks 1.1.0, we were bound to make a mistake. It looks like image replacement was that mistake. Stacks 1.1.1 comes to the rescue. We've corrected the issue and you can now drag to replace images again.

For more details on the features and fixes we made in big Stacks 1.1, check out the big list.

Stacks: Get it Now