Rev has built-in support for basic dialogs using the answer and ask commands. But sometimes your application needs to display a customized dialog to the user. The dialog may prompt for some user input or merely alert the user about something. In this case you need to create a stack that acts as your modal dialog (you can make the dialog stack as a substack of your main program stack).

This lesson will show you how to use the dialogData global property to pass data from the handler that opens the dialog to the modal dialog stack itself, and then back again. The dialogData is a special global property reserved especially for passing data back and forth between a dialog window and the handler that opens the dialog window.

This lesson will show you how to make a color picker swatch.

It is often the case that stacks need to be resizable particularly when they may contain a variable volume of content. This can be problematic if you have spent a great deal of time making a visually impressive stack and have a large number of controls to reposition and resize. The geometry manager is a good way to solve this problem and can save you a great deal of time writing resize handlers. Having only been working at Runtime for a short time I'm still very much in the learning process. When designing stacks I initially found the geometry manager to be a little confusing, and now that I understand how it operates I thought that this newsletter would be a perfect opportunity to go through its basic features.

Its basic function is to allow you to adjust the way that controls are scaled or reposition themselves when the stack is resized. In order to explore the functionality of the geometry manager, we will first need to import an image to experiment with. There are several ways of doing this in revolution, but perhaps the easiest is to create an image object and specify it's filepath using the property inspector.

In this lesson we look at cards and how to add a new one to your stack.