Problem creating or modifying a run config

Hi all,

I am writing here because I have recently updated eclipse, and I am having issues trying to add a new run config or modifying an existing one. I have two issues:

- Parts of the running config like the name or the API level cannot be seen properly

- Everytime I try to add a new run config there is an issue that can be seen on the left side of the image which says "Index Out of Bounds"

The problem can be seen in the following image.

Eclipse version is 2023-06 (4.28.0), build id: 20230608-1333, and Connect IQ version is 4.1.2 for both the IDE and the SDK manager (seen in Eclipse through Help->Install new software)

Do you have any ideas of what may be wrong?

Thanks,

Javier

_psx_ over 2 years ago

The problem is because you have downloaded new devices!

Garmin has changed (I think without any reason) the minimal version of firmware/ciq in compiler.json for devices. It even force users to upgrade firmware to the latest (often bugged).

You have 2 choices

- modify compiler.json (decreasing versions) and use sdk 4.x

- use sdk 6.x

jim_m_58 over 2 years ago in reply to _psx_

Unless directed to change a compiler.json by Garmin, it's shouldn't be done. There are reasons Garmin changed them in the first place and you don't know the impact.

Eclipse is no longer supported. Time to move to VS Code as the first version of that has been out for 2+ years.

_psx_ over 2 years ago in reply to jim_m_58

The only reason to increase version is compatibility new compiler with something in firmware but it is not true because I know that users of my apps have new firmware (13.22) and app 4.x (I have older firmware - 11.28 and beta version 6.x and it runs without any problem).

If somebody wants to use e.g. vector fonts from 6.x he needs new compiler and new firmware but if I use only stuffs below 6 I can compile app with 4.x and 6.x (but compiler.json doesn't allow it) and it should run well.

jim_m_58 over 2 years ago in reply to _psx_

Let's save there is a FW bug related to CIQ that was fixed in newer FW. The bump could be to insure the user is running the fixed FW.

As far as SDK, you want to stay current, as there are bugs fixed there too.

Maybe you've been lucky, but hacking the device files is not something I'd suggest, as you may run into stuff that you don't run the standard devices..

_psx_ over 2 years ago in reply to jim_m_58

Yes, I also believe that you should use the latest version of the sdk and devices but ... bugs in new sdk!

I've reported that in 6.2.0 onStop() is no called, in 6.2.1 bug hasn't fixed so now I should rewrite all code based on onStop() to test app... No, I don't want to waste my time for stupid work and have to find workaround...

_psx_ over 2 years ago in reply to jim_m_58

And I want to use 6.x because it fixes bug reported months ago:

Fix a bug where the if / else if block could clear member typing in the subsequent else / else if blocks.

Javier M.A. over 2 years ago in reply to _psx_

I chose the 2nd option and it worked, so many thanks!