• Replies 11 replies
  • Subscribers 20 subscribers
  • Views 2486 views
  • Users 0 members are here
Options
Related

The Instinct2/s require VS Code to run the sim.

jim_m_58

Just a heads up, but if you want to port something to the Instinct2/s, you need to use VS Code, as the device has CIQ 3.3.x, and eclipse doesn't allow that when running the sim.

.Supporting a new device in eclipse isn't the same as adding a new feature (like the debugger) in eclipse in my opinion

  • People should already be using VS Code. They should know Eclipse for IQ is a dead end.

    The new guide makes it easier to pick it up.

  • I agree with Jim, a new product is not a new feature. This topic would be rather suited to be placed inside bug reports than within the discussion forum though.

    There's a workaround to make it work in eclipse but you have to to go edit the files in the device folder to make the 3.3 a 3.2, noone should be forced to go down that route, editing configuration files is messy.

    While I moved to vscode (and like vscode) for most things, some things work just better in eclipse (unit testing, getting device specs, ....) and I do use it concurrently.

    @dpawlyk also it's not because you and I like vscode better, that people who like eclipse better should be forced to move. The news item clearly stated that the plugin would still be maintained. Not supporting some products is not equal to maintaining the plugin in my book.

  • in reply to peterdedecker

    You make a case for using both. What I said doesn't actually contradict that.

    The Instinct2 is in a beta version of the SDK. Maybe, Garmin doesn't release beta SDKs to Eclipse?

    People should move to VS Code because that's what Garmin is moving to (people don't really have a choice).

  • in reply to dpawlyk

    It's in the production 4.0.10 SDK, and apps can be published for it.

    While I started using VS Code (along with Eclipse) back in Oct 2020 when it was first announced, there seem to be many people that are still only using Eclipse.

    The Instinct 2 is going to be an interesting device to support to begin with, and I'm not sure that making people move to VS Code at the same time is wise.  It's just a new device, not a new feature.

  • in reply to jim_m_58

    I only see "4.0.10 Beta 1" in the SDK manager (event just now).

    More "interesting" than interesting. Looking at the announcements, it was "WTH?".

  • in reply to dpawlyk

    The order of the SDKs in the SDK manager is odd, and 4.0.10 is between 4.0.1 and 4.0.2

  • in reply to jim_m_58

    Ugh. I didn't look that far down in the list. It's sorted alphabetically.

    New device! New SDK (at the top)!

    The SDK manager thinks 4.0.9 is newer than 4.0.10.

    Ugh.

    My app crashes in the sim for the Instinct2. (If it was a missing feature, I would have expected a different error).

    Encountered app crash.
    Failed to launch the app: Timeout

    Ugh.

    The Instinct2 isn't in the beta (the Instinct2s is).

    Ugh.

    (I might just skip this one.)

  • in reply to jim_m_58

    yes, I wasted some time before noticing this feature in sorting

  • I just pushed new device files to download using the SDK Manager for the Instinct 2 and Instinct 2s. Once you download the updated files Eclipse should be able to run these devices. Eclipse should work in the near future for new devices. This was a something we overlooked for 3.3 and 4.1 devices. 

    I've also corrected the ordering issue in the SDK Manager, but it'll require a new SDK Manager release. That will be coming with the official launch of 4.1.

Copyright © 1996-2025 Garmin Ltd. or its subsidiaries