Issues with sdk 4.0.6, VSCode and MonkeyC plugin 1.0.0 for MAC

I'm experiencing multiple issues with a combination of SDK 4.0.6, MonkeyC plug 1.0.0 on VSCode on a MAC. Is anyone else?

- Launching an app from VSCode does not appear to be picking up the right reference in my jungles file - or does not recognise the App connected to the source file I currently have open. It builds for a completely different App. Does not happen with MonkeyC plugin 0.1.13 (and SDK 4.0.6)

- When the simulator loads I'm presented with a blank window. I have to shutdown and restart the simulator, sometimes multiple times. Does not happen with MonkeyC plugin 0.1.13 (and SDK 4.0.6)

- With SDK 4.0.6, double-clicking the memory stats at the bottom of the simulator window causes the simulator to crash and generate a problem report to apple. This does not happen with sdk 4.0.5.

VSCode does not let me rollback the MonkeyC plugin to anything more recent than v0.1.13 (even if I uninstall and reinstall). I'm not sure I should even be able to select 0.1.13 and SDK 4.0.6 in combination, but I can.

My environment:

macOS v11.6 (macbook pro 2019)

VSCode v1.61.1

Connect IQ SDK 4.0.6

MonkeyC VSC Plugin 1.0.0

Java 1.8.0_271

Top Replies

jim_m_58 over 5 years ago in reply to el34rob +1

When you go to extention settings, you can go to folder and set the settings. I've not tried this, but it looks like you can set typeCheckLevel for a project here per project.

Here's what you see…

All Replies

li2niu over 5 years ago

el34rob said:
When the simulator loads I'm presented with a blank window. I have to shutdown and restart the simulator, sometimes multiple times. Does not happen with MonkeyC plugin 0.1.13 (and SDK 4.0.6)

I encountered this problem as well. I think you can disable vscode from automaticly updating and install another version of vscode plugin ie. 0.1.13

el34rob over 5 years ago in reply to li2niu

That doesn't work for me - at least on MAC. turning on/off auto updates makes no difference to the list of available updates - there is nothing newer than 0.1.13 (apart from 1.0.0), regardless of whether I choose SDK 4.0.5 or 4.0.6

el34rob over 5 years ago in reply to el34rob

I've raised a bug for the View Memory crash (including Apple problem report), here: Crash with Simulator View Memory, SDK 4.0.6 on a MAC - Connect IQ Bug Reports - Connect IQ - Garmin Forums

Will do the same for the first issue I listed when I get a chance.

jim_m_58 over 5 years ago in reply to el34rob

What if you use the 4.1.0-beta1 SDK on a mac? It could be a fix is already there or it's broken there, but something to note in the bug report.

el34rob over 5 years ago in reply to jim_m_58

Just tried that Jim. Still crashes under 4.1.0-beta1. I'll update the bug.

jim_m_58 over 5 years ago in reply to el34rob

Sounds like it will be in both Eclipse and VS code as it's the sim on the mac. I'm on Windows and don't see it in either

el34rob over 5 years ago in reply to jim_m_58

So, it looks like the first issue I raised in this thread (building for the wrong app) is not an issue under 4.1.0-beta1 (at least on a MAC). The second issue I raised is still an issue - but I think a bug has already been raised for that.

jim_m_58 over 5 years ago in reply to el34rob

As far as running stuff, the way I understand it (I may be wrong) with the 1.0.0 extension, there is a launch.json involved, and the way you use (or create one) is using the play/debug symbol on the left. Here I did that, clicked on "Run App", then create config for PiTemps, than ran that. You still need to use the run menu (I use run without debugging), to do the build and start the sim.

It's easy to switch projects, and don't require anything to be opne in an editor window. If I want to switch to SimBar, I just select "Run App (SimBar), and then use the run menu to fire it off.

el34rob over 5 years ago in reply to jim_m_58

Thanks Jim, I stumbled on that too, but wasn't sure what to make of it - I was so used to right-clicking on a project and selecting build and pressing ^F5. But now, I see some potential here. I wonder if the launch.json file could have the ability to store the "monkeyC.typeCheckLevel" setting for each app??...

I've got one app written in 'Strict' mode and all the others in 'Default' - it's a PITA having to change this setting depending on which app I'm updating (I may never update them all to Strict).

I tried adding "monkeyC.typeCheckLevel": "Default" (and also "typeCheckLevel": "Default") into the launch.json but alas, it had no effect :-(

flowstate over 5 years ago in reply to el34rob

el34rob said:
I was so used to right-clicking on a project and selecting build and pressing ^F5.

If I have one or more projects open in a VS Code workspace, it works for me to open any .mc or .jungle file, and press F5. It builds the current project and launches the sim in one step. (If you haven't built before it prompts for the device to build, otherwise it uses the last built device.)