As of right now you can't do that with CIQ Watch faces.  The GDVC is on Oct 12, and there is a breakout called: 

Connect IQ: Complications That Aren't Complicated

Stay tuned.

https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/join-us-at-the-garmin-developer-virtual-conference

So was it what you expected??? My google-foo don't seem to find any news on this. Can only find this: forums.garmin.com/.../welcome-to-connect-iq-system-6

The video from the breakout should be posted any day now.  I watched it live. There is also this in the doc that is in the 4.2.0 beta doc when you install it: under core topics

Complications

Garmin devices collect numerous data points as users wear them. Many of these data points can be summarized and displayed on the watch face as a [complication](en.wikipedia.org/.../Complication_(horology). The Connect IQ SDK offers multiple APIs to access user metrics, and has expanded the offerings with every release.

The Toybox.Complications module consolidates the specific metrics typically displayed by Garmin devices into a unified interface. This unified interface gives the developer access to the information typically shown on the watch face for the developer. The complications are exposed using a publish/subscribe model.

In addition, device app and audio content provider developers can now publish up to four complications using this new framework. Complications have public, protected, and private visibility levels with the system.

Finally, Face It will also be a consumer of Connect IQ complications. This allows developers to create information that can be published on Face It watch faces.

Publishers and Subscribers

At the heart of the complications system is a publisher/subscriber system. The system publishes complication data for subscribers to consume. Connect IQ device apps and audio content providers can publish complication data, but only watch faces can subscribe to complication information.

Complication Objects

Data is published as a Complications.Complication object. The complication object exposes the following information:

You can query additional information with these accessors:

Units

Complications are allowed to publish information in units that are configurable by the user in their system settings. When receiving complication values, it is the subscriber’s role to convert the value to the metric specified in system settings.

Units should be expected to be published as the following:

Subscribing to Complications

To publish a complication you need to add the ComplicationSubscriber permission to your manifest file. Subscribing to Complications requires the Id. You can use Complications.getComplications() to query the identifiers of all complications supported by the system:

// get an iterator over complications available to this app
void iter = Complications.getComplications();
// iterate over them
var complicationId = iter.next();

while (complicationId != null) {
    var complication =
       Complications.getComplication(complicationId);
    complicationId = iter.next();
}

You can also query a native complication directly by constructing a Id explicitly:

var complication = Complications.getComplication(
    new Id(Complications.COMPLICATION_TYPE_CALORIES)
);

This only works for native complications. Once you have the complication id, you can persist the id in storage for later use.

You can use Complications.registerComplicationChangeCallback() to subscribe to multiple complication values. All subscriptions are terminated when your app shuts down and must be re-done when your app is launched. When you subscribe, you register a callback to be called when the value updates:

function onStart(params as Dictionary) as Void {
    // Retrieve persisted Complication ID
    mComplicationId = Storage.getValue(COMPLICATION_ID_KEY);

    // Register a callback for receiving
    // updates on complication information
    Complications.registerComplicationChangeCallback(
        self.method(:onComplicationChanged));

    // Liking and subscribing
    Complications.subscribeToUpdates(mComplicationId);
}

In your callback, you can then query the updated information and process it:

function onComplicationChanged(
    complicationId as Complication.Id) as Void {
    // Identify the complication being updated
    if (complicationId == mComplicationId) {
        // Get the complication information
        try {
            var data = Complications.getComplication(
                complicationId);
            // Handle the application processing
            updateData(complicationId, data);
        } catch (e instanceof ComplicationNotFoundException) {
            handleComplicationRemoval(complicationId);
        }
    }
}

If the complication is no longer available, for example the user has uninstalled the publishing app, the system will throw a ComplicationNotFoundException. You should trap this exception and handle it within your app. If a publishing app is uninstalled, the system will send an event to your ComplicationChangeCallback and automatically unsubscribe your app from any subscribed complications.

Hold to Launch

Some Connect IQ products have a feature where pressing and holding on a complication launches the associated app. You can add this functionality to your watch face by implementing the WatchFaceDelegate.onPress() method:

function onPress(clickEvent as ClickEvent) as Boolean {
    if ((mComplicationId != null) &&
         isClickInside(clickEvent, mBoundingBox)) {

        // launch the app that published the
        // complication
        try {
            Complications.exitTo(mComplicationId);
            return true;
        } catch (e as AppNotInstalledException) {
            // fall through
        }
    }

    return false;
}

Publishing Complications

If you are developing a device or audio content provider apps, you can publish up to four complications to the framework. To publish a complication you need to add the ComplicationPublisher permission to your manifest file.

Resources

To publish a complication, you have to define each complication in your resources:

    <complication id="0" access="public"
                  longLabel="@Strings.myLongLabel"
                  shortLabel="@Strings.myShortLabel"
                  icon="@Drawables.MyComplication"
                  glancePreview="true">
        <faceIt defaultText="@Strings.complicationName" />
        <range>
            <value>0</value>
            <value>24</value>
            <value>33</value>
            <value>41</value>
            <value>50</value>
            <value>53</value>
        </range>
    </complication>

The complication element has the following attributes:

Using the access attribute, you can control if your complications are visible to just apps with your developer key, all apps, and Face It or all of the above:

The required faceIt element allows you to provide information for Face it:

The optional range element allows you to provide an ordered set of numeric values that define different ranges for your value.

Publishing Values

Once your complication is defined, you can use the Complications.updateComplication() function to publish data:

var data = {
    // String, Number, Float, Long, Double, or null
    :value => newValue,

    // String
    :shortLabel => newShortLabel,

    // String or Complication.UNITS_* value
    :units => newUnits,

    // Array<Numeric> with at least 3 elements
    :ranges => newRanges,
}

// update complication
// 0 is the id of the complication
// from complications.xml
Complications.updateComplication(0, data);

Face It (Coming Soon)

Publishing a complication as public allows Face It to integrate your complication. It will always display your complication icon, and will use the following rules to display your complication value:

Cool. Thanks.

remember, with the 4.2.0 beta SDK, you can't export/build an iq file, and devices with System6/a CIQ 4.2.x VM won't be available for probably a couple months, so sideloads won't work either.

hi! I did some test with the beta with onPress (maybe not deep enough)

it seems doing it does not turn the device on HighPowerMode, did you see that somewhere?

In my opinion it should do it no? or did I miss something? or it is normal? since we can't test it on real.

Not sure I ever said that, unless it's somewhere in the garmin doc I posted.  In my opinion, in the sim, the watch face should stay in what ever power mode it was in, but the delegate should be called for the onPress..

sorry for the misunderstanding, I did not say you said that, I asked to you because I known you atempted the Garmin Conference and just asked if you heard about that in it. I wanted your opinion about that, what you gave me so thanks.

When you move the watch to do the onPress, I think it's likely the WF will drop out of low power mode due to the gesture. On touch devices tapping/pressing the screen will probably drop it out of low power mode, even without complications