This seems weird. Big jump to SDK 6? And a dramatic reduction in size?
NOTE: In Eclipse I had to go into PREFERENCES and manually point to the new SDK. The SDK Manager did not update that from SDK 4.2
This seems weird. Big jump to SDK 6? And a dramatic reduction in size?
NOTE: In Eclipse I had to go into PREFERENCES and manually point to the new SDK. The SDK Manager did not update that from SDK 4.2
1) SDK 6.2.0 no longer allows IDs with start underscore - e.g. _myName, which I do with all Resources/Setting IDs. So there is a lot of work waiting because I have to change the IDs.
2) if I therefore do…
What will the version number look like in 2024 q2 when there will be no system7?
6.12.0?
Yes - I, too, rolled back to previous 4.version and then all Edge x40 devices crash on simulator (on every dc. Command like dc.fillcircle….)
I‘ve just testet a small datafield with Edge 1040 and…
Just so I'm clear... every CIQ app, widget or data field that has one of these *40 EDGE devices in our supported devices list, must be rebuilt and uploaded to the store?
Only those that you uploaded since the version of the devices that were available since the 6.2.0 SDK was released.
The new update to the edge x40 devices fix a min FW bug that was introduced with those device files.
ok so yes for me. Thanks! You also need to wait until this:
Correct—it's likely if you built and uploaded a version of your apps that support Edge 540, 840, or 1040 since 6.2.0 was released, your users will encounter and error when attempting to install your apps.
The online docs say this:
But setProperty and getProperty are now gone, like they were threatened to be, so this new version doesn't really support the old devices like it claims. Did I miss the "these devices are no longer supported" list with this version somewhere?
Before SDK 6.2 a class could see a public var in another class. Now it "Cannot find symbol" when compiling. What's the new trick?
New trick is to declare something like myvar in the referencing class as a type of the referenced class, then use the new myvar.otherClassVar to see it.
But setProperty and getProperty are now gone, like they were threatened to be
I'm not seeing this, they are still working for me. Don't think they can be removed until a mechanism is provided to use them for the older devices which do not support get/setValue and allow you to package a single app built with different SDK versions.
Same here and getProperty/setProperty are working fine for me with the 6.2.1 SDK on devices without setValue/getValue like the original vivoactive and new devices like the fr965
Why am I seeing this? Did it move?