this is just to save people some time who might be hunting for the SDK samples folder.
In MacOS, mine was here:
/Users/YOURUSERNAMEHERE/Library/Application Support/Garmin/ConnectIQ/Sdks/YOURCONNECTIQSDKVERSIONHERE/samples
this is just to save people some time who might be hunting for the SDK samples folder.
In MacOS, mine was here:
/Users/YOURUSERNAMEHERE/Library/Application Support/Garmin/ConnectIQ/Sdks/YOURCONNECTIQSDKVERSIONHERE/samples
You can also open the samples folder from VS Code by using the command palette (CMD-SHIFT-P on Mac / CTRL-SHIFT-P on Windows) and selecting "Monkey C: Open Samples Folder".
In macOS, from the…
Yeah that's super annoying. I imagine the vast majority of those are errors are type checking errors.
You can try adding the following line to monkey.jungle, as a quick fix:
project.typecheck = 0
…You can also open the samples folder from VS Code by using the command palette (CMD-SHIFT-P on Mac / CTRL-SHIFT-P on Windows) and selecting "Monkey C: Open Samples Folder".
In macOS, from the Terminal app, the path to the current SDK folder can be printed as follows:
cat ~"/Library/Application Support/Garmin/ConnectIQ/current-sdk.cfg"
e.g. To open the SDK sample folder in Finder, the following command can be used:
open "$(cat ~"/Library/Application Support/Garmin/ConnectIQ/current-sdk.cfg")/Samples"
Here's an official doc for CIQ command line usage:
[https://developer.garmin.com/connect-iq/reference-guides/monkey-c-command-line-setup/]
Yeah that's super annoying. I imagine the vast majority of those are errors are type checking errors.
You can try adding the following line to monkey.jungle, as a quick fix:
project.typecheck = 0
(I recommend using type checking in general tho.)