• Replies 5 replies
  • Subscribers 15 subscribers
  • Views 408 views
  • Users 0 members are here
Options
Related

Corrections to documentation for Connect IQ

dbrobert
over 8 years ago
Is the documentation for Connect IQ (online or within the SDKs) actively maintained? If so, where should we report errors, omissions, corrections, etc?

As an example, the TextPicker page only mentions three devices are supported but that list should include the D2 Bravo. And further to that, the Keyboard sample app includes the vivoactive in the list of devices but then the forum thread "Anyone used a textpicker on vivoactive?" has a post from Kyle.ConnectIQ saying that vivoactive will never get a TextPicker.

Thanks,
Douglas
  • Former Member
    Former Member over 8 years ago
    These forums are the best way to report any Connect IQ issues you're seeing. I've created a ticket to update the list of supported devices in the TextPicker documentation.

    I don't believe the Keyboard app supporting the vivoactive is an error. If you look at the code of the app there is a has :TextPicker check. If the app is run on the vivoactive you will simply see a message indicating the TextPicker isn't supported. I think the point of including it is to show you can include a device that doesn't have an API you're using in your app and the app can run safely. The usefulness of this particular app if you can't use the TextPicker isn't really there but the vivoactive is included to make a point.
  • over 8 years ago
    Ah, okay. I was confused because the simulator ran the app and displayed the TextPicker.

    I will make notes of documentation fixes and post them in a new thread.

    Cheers,
    Douglas
  • over 8 years ago
    If you look at the code of the app there is a has :TextPicker check.


    That check is only in the examples within SDK 2.1.x, in case anyone is looking for it. I was referring to SDK 1.2.x, which I am limited to due to building for the D2 Bravo device.

    Cheers,
    Douglas
  • over 8 years ago
    You should be able to build for the D2 with the 2.1.0 preview but you can't use any of the new 2.1 functions and you just can't upload to the store until the 2.1.x SDK is released.

    Have you looked at the generic Picker instead of the TextPicker? The TextPicker is only on a few devices, but the generic will work on everything.
  • Former Member
    Former Member over 8 years ago
    Ah, okay. I was confused because the simulator ran the app and displayed the TextPicker.


    This is a limitation of the simulator. APIs are not being "turned off" based on the device being simulated. I know this ability has been discussed multiple times before and I think we have plans to do so but I don't know any specifics.

    That check is only in the examples within SDK 2.1.x, in case anyone is looking for it. I was referring to SDK 1.2.x, which I am limited to due to building for the D2 Bravo device.


    If this is fixed in the 2.1.0 SDK then this won't be fixed in a CIQ 1.x.x SDK release. Once the 2.1.0 SDK is officially released (non beta) we will stop releasing CIQ 1.x.x SDKs. However, you can use the 2.x.x SDKs to build apps for devices which run the 1.x.x VM (the compiler is backwards compatible). You should still be able to use the CIQ 2.x.x SDKs to build apps for your D2 but you won't be able to use any of the new APIs unless they get back-ported to the 1.x.x VM.