Yes, global counters can work from any page, including page 1. I tested it today to make sure.

Yep, once the folder is ready in your Downloads folder, you can move it to Documents / InteractBuilder / [the name of the project group you're using]. Then it should be available in InteractBuilder.

Here's an example of a custom palette: Custom Palette Sample.

Here's how I set up the page in the attached example:

1. Set the palette elements to be invisible at runtime and assign them to group 1. This includes the element that should be used to close the palette. In this example, it is a white screen behind the palette.

2. To each color on the palette, add a Tap-SelColor action set, using the specific color that it represents. You can set the RGB values of each color based on the values the element has in Photoshop (or other image-editing program that you are using to create the color palette). You can also include a -FillColor (last selected color) action set chained after the first one if you'd like a specific element to change to the selected color. In the example, the paint on the brush changes to the selected color so that the user can see the color that has been selected.

3. To the element that should close the palette, add a Tap-HideGroup 1 action set.

Before a color is selected, the default FillColor color is black, so in this example, I set the blue SelColor behavior to also happen on page load. So the color on the brush is blue, and the first color that can be used is blue.

I'll send you a link here to a simple version of this effect with just a few colors to show you how it works. I think the great thing about building a color palette in this way is that you can design it to match the style of your app. This way, you also have an option to have the color palette always available on the page so that the user does not have to keep opening and closing it.

Hi there,
This might be because we've updated the way the coordinates are set up. We used to have the bottom left corner of the screen set to (0,0), but we have since changed it to the top left corner, to match the standard that image editing programs use. Here's what you can do to get your scrollable background working:

1. First, for this situation, it's simpler if you set the graphic element to not be a scrollable element. You can change this in the element's properties. Set the Scrollable Background field to No.

2. In the element's Properties, make sure the size of the element matches the size of the original image (in this case, 768 x 2048), and set the element's Anchor Point to Middle-Center.

3. If, like in the screenshots you attached, you have the element starting with its top edge at the top of the screen, then the constraints for the Drag-Move (Self) action set should be the following:
Left: 0
Top: -1024
Right: 768
Bottom: 2048

I think it might not be a very quick fix since it involves adjusting the design of the color selection window and since it is more of an improvement than a bug fix, but if you don't mind having fewer color choices I would recommend creating a custom color palette that fits well with your app. You can design a palette with a separate graphic element for each color choice, each with its own Tap-SelColor action set. If you add a group number to each element that is part of the color palette, then the buttons for opening and closing the palette can just use the ShowGroup and HideGroup behaviors, respectively. Let me know if you'd like to see a sample app that uses this kind of menu.

Hi Sean,
Here's a way to get around this problem:

1. On the pages that have CounterDisplay on page load, add a text element, and use that as the target of the CounterDisplay behavior. The CounterDisplay behavior has a separate field for Target and Counter, and the Counter field is where you can select the global counter that will display in the Target text element. So the global counter keeps track of the value, but the text elements on each page act as a container for displaying the value.

2. On the pages that use CounterDisplay on page load, go to the page properties, and set the Save Page State field to No. This makes sure that the "on page load" behaviors happen each time the page opens.

Yes, InteractCloud should be working. Are you signed in with the same account on both computers?

Ok, thank you!