Newbe - Silly Questions

Each DF is actually it's own .prg file, with it's own manifest ID (a compiled piece of code).  To build a prg, it can be one or more .mc files, and depending on how you want to do things, each DF could have it's own ,mc file(s), or using shared file(s) between different DF's.

The easiest way to start is each DF has it's own .mc file(s) and in eclipse is a separate project - so you'd have projects called df1, df2, etc for example.

As far as the onSelect() thing, input delegates can only be used on some non-wearable devices (edge bike computers with touch screens) and then, only onTap() is available.

Do you have a CIQ device?  if so, you might want to sideload a prg file for a DF and see how that works.  See the new developer FAQ wiki and programmer's guil;d to learn about sideloading.

What Jim said.  But in addition, on most wearable devices (watches) you can only use 2 data fields at a time.  On some Edge devices you can use up to 10.

You can always use "onLap" to trigger your event code, but there will also be an actual lap recorded in the activity file.

Ok - First thanks for taking the time to respond. There is very little tutorials on this availble

Conceptially is 1 DF, displaying 1 thing.... Ie it could be UTC Time, or elapsed time or distance to next waypoiint? is that 3 seperate DFs? I believe my watch supports up to 6.

What is the purpose of the DF ?  To return a number ?

Or can this be done in other places like View also ?

Could I somehow output several different numbers using one DF?

Like Time / Dist / Speed etc?

I'm generally trying to use activity.info to refresh values on  screen once a second

Im also not sure in eclipse, how to I run 2 projects at one.... or do you link to the other project to get values in another project?

In eclipse, you an only run one DF at a time.  It sounds like you've only looked at simple data fields, where in compute() a value is returned to display.  There are also complex data fields, where they do their own drawing, and you can display a number of different things at the same time, so a single DF could display UTC, elapsed time, etc, at once.

As far as changing, an approach I read about just the other day, is to do a change based on moving between data screens, so for example, if your data field is on screen 1, you move to screen 2, and back to screen 1 in a short amount of time, what's displayed in your data field could change.  Gar better that using the lap button and messing up the .fit file.

I see, are there any examples of a complex datafield in the SDK example pack that you can recomend?

I used the simple one as a guide, which I copied to try and make an output, but nothing in the example pack is labelled complex.

My understanding is that the code is run in seguence from the app.mc, which then starts the initial views delegate etc...

once  a view is called in.... If there is functions inside that view and another view is called in does the functions in the initial view stop?

If someone has any time, looking at this code, would it work? ( ignoring the { } I had to manually put spacing in there on this forum)

using Toybox.WatchUi;
using Toybox.System;

class AngleOffSimpleDataField extends WatchUi.SimpleDataField {

function initialize() {
SimpleDataField.initialize();
label = "Angle Off";
}
function compute() {

var AO = "----";

 if(info.track != null) {
  if(info.bearing != null) {
   if(info.track >= info.bearing) {
    if(toDegrees(info.track - info.bearing) > 180) {
      var AO = 360 - toDegrees(info.track) + toDegrees(info.bearing) + "R";
      }
    if(toDegrees(info.track - info.bearing) <= 180) {
       var AO = toDegrees(info.track - info.bearing) + "L";
      }
     }
   if(info.track < info.bearing) {
     if(toDegrees(info.bearing - info.track) > 180) {
        var AO = 360 - toDegrees(info.bearing) + toDegrees(info.track) + "L";
        }
     if(toDegrees(info.bearing - info.track) <= 180) {
         var AO = toDegrees(info.bearing - info.track) + "R";
        }
     }
   }
  }
return AO;
 }
}

You can't see button presses in a data field as you propose. 

In Eclipse, do a File>New>Connect IQ Project, and set the app type to be a Data field. and when asked "simple" or "complex", select complex