Installing Garmin IQ SDK

Have you installed VS Code and the Monkey C Extension?

See https://developer.garmin.com/connect-iq/connect-iq-basics/getting-started/

Oops, do I need that now? Up to Version 3 a texteditor was enough and the batch files did the rest

Will the VS code create the device.xml file so that I can start the simulator from the command line? When I use the simulator now it returns something like "no device found"...

devices.xml is no longer used.  That's why you now download the separate device files.

On windows the SDKs are now under appdata\roaming\garmin\connectiq\sdks in the user's directory.  You'll find the scripts for running the command line there.

Hi, thanks for youa r hints, anyhow something seems to be wrong here...

I got the Fonts and the devices in the AppData folder but do not find any script there (.bin, .json, .png and a .xml file), starting the simulator by 'connectiq.bat' shows 'unable to connect to a ANT device; No device found"...

I've tried to adapt my old batch files, but no FR955 will be found...

-----

echo off

set devices=* 0-round_watch 1-edge_1000 2-fr235 3-fr935 4-fr920xt 5-fenix5 6-fr630 7-fr735xt 8-edge820 9-fr955 e-epix g-oregon7xx h-vivoactive_hr i-rino7xx v-vivoactive x-fenix5x
set bugfix=C:\Users\%USERNAME%\AppData\Local\Temp\GARMIN\APPS\
set devlist=%devices:~2%

set add=C:\Program Files\System\Java SDK\jre\bin
echo "%path%"|find "%add%" > nul || set path=%path%;%add%

:help
if '%1'=='?' (
    echo.
    echo Usage: test [program [watchtype]]
    echo.
    echo Watchtypes:
    echo -----------
    :showlist
    For /F "tokens=1* delims= " %%A IN ("%devlist%") DO (
        echo %%A
        set devlist=%%B
        if NOT "devlist%"=="" goto showlist
    )
    
    goto :eof
)

:tasks
tasklist /FI "IMAGENAME eq simulator.exe"|find "simulator.exe">nul
if not errorlevel 1 ( goto :checkparameter )


:init simulator
echo Start simulator...
bin\simulator

 
:checkparameter
if '%1'=='' (
    set prog=%sample%
) else (
    set prog=%1
)

set proginfo=%prog%
echo "%prog%"|find ".prg" > nul || set prog=%prog%.prg
echo "%prog%"|find "\" > nul || set prog="%~dp0%prog%"

set face=%2.
set face=%face:~0,1%

setlocal enabledelayedexpansion
    : get device from parameter (0-9)
    call set face=!devices:*%face%-=!
    call set face=%face: =&rem.%
    : get device from last compiler configuration
    if %face%==* (
        call set face=%flags%
        call set face=!face:*--device =!
    )
    call set face=%face: =&rem.%
    : if no information present set to default watch face
    if /%face%==/*--device set face=round_watch
endlocal & set face=%face%


:run
echo.
echo Try to start '%proginfo%' for device '%face%'...
echo ----------------------------------------------------------
if exist %bugfix%\. (
    call set dirfilter="%proginfo%"
    dir %bugfix%| find /I %dirfilter% 2>nul
    copy %prog% "%bugfix%">nul
    echo ----------------------------------------------------------
)
:echo bin\monkeydo %prog% %face%
bin\monkeydo %prog% %face%

---

The batch file are in the bin directory within an SDK.  Just like they were in older SDKs.  Monkeyc, monkeydo, etc

Thanks being patient with me...

...yes, I tried the batches in the bin folder also (connectiq.bat is used to start the simulator), but they just don't work :(

Forgot to mention that the SDK manager has shown a box that it's internal script has a problem (when a dialog appeared with all new devices available), but cam be continued. And now I have one installation on a Windows 8.1 and one on Windows 10 and both don't like the SDK 4.1.3 (or me)...

UPDATE: still not running as expected, but I'm getting forward , I'll post another update as soon as possible...

Got it to work, now I need to refresh my Screeny-Tool to do keep my slim development solution. I will see if anything else has to be done except changing the parsing of the device.xml (I need that to read the simulator parameters, this allow to make screenshots or to use shortcuts to control the watch in the simulator).

I could compile one of my widgets (okay glance) already, next steps are to tune the fonts (that's why I updated ScreenyFont which is quite good now) for the higher screen resolution and add touch support (which seems not so easy, I'd need an example source)...

Again, thank you for your help.