2.3.1 compiler/simulator problem

I was using an older SDK, just had extracted all files from the zip file and started to program - a datafield, an app, a watchface and now a widget - and all worked fine on the simulator as well as on my watch.
Now I was doing the same with the new 2.3.1 SDK, but the simulator does not feel ready to show any of my compiled prg files - only a small garmin logo is seen on the display, that's it.

Any ideas what is going wrong here?:confused:

PUFFOLINO over 8 years ago

Is anyone able to start a program within the simulator from the command line window? I have tried to do so on six different computers now, wrote a prgram to catch the parameters for the shell.exe, checked "everything", I have no idea why the new simulator does not work here. :(

PUFFOLINO over 8 years ago

I noticed yesterday that the updated 'Make' you posted still has the "round_watch" and "square_watch" device profiles listed. Is there any chance you are trying to use those? In the 2.3.1 release the simulator no longer supports those generic profiles, with the intention being that you use specific device profiles for testing.

Yes, the generic devices are here (for backward compatibility :rolleyes:)
No, I am doing an echo to view the parameter and the chosen watch will be seen in the simulator (but nothing else :mad:)

Screen shot

Former Member over 8 years ago

Is anyone able to start a program within the simulator from the command line window? I have tried to do so on six different computers now, wrote a program to catch the parameters for the shell.exe, checked "everything", I have no idea why the new simulator does not work here. :(

I am able to launch prg's just fine with both monkeydo scripts from the command line. Is this failing for you only when you run your make script, or is it also failing if you manually call 'monkeydo.bat SomeApp.prg fr935' on an app that you know runs without crashing?

PUFFOLINO over 8 years ago

I am able to launch prg's just fine with both monkeydo scripts from the command line. Is this failing for you only when you run your make script, or is it also failing if you manually call 'monkeydo.bat SomeApp.prg fr935' on an app that you know runs without crashing?

It fails completely in (nearly) all cases, it doesn't matter if I use 'make', 'monkeydo' or entering the command line (something like 'java -classpath "[...]monkeybrains.jar" com.garmin.monkeybrains[...] -f Mickey.prg -d fr935 -s "[...]\shell.exe"')

The only case where the prg file shows at least something on the screen are datafields - anyhow the results are still useless.

Former Member over 8 years ago

The inverting text is probably due to a known issue that should be fixed in the next release, I believe it is also mentioned in the bug report forum linked below. As to why the other apps are failing, and potentially other graphics issues, would you be willing to send us some of the prg files you are seeing this with? I can then take a look and see exactly why it's happening. Those files can be directed at either ConnectIQ at garmin.com or my username at garmin.com.

https://forums.garmin.com/showthread.php?375171-2-3-beta-1-getBackgroundColor

PUFFOLINO 24 days ago

Around 10 years later...

...I'm still compiling my programs by using a 'simple' batch file - here it is my selfmade script for everyone who wants to keep it simple ;-)

You've to put the batch into the project path (where monkey.jungle stays) and adapt the settings in the lines (mypath and myapp are optional):

set iqpath=C:\Tools\Garmin\Connect\v8.2\Bin
set mykey=C:\Tools\Garmin\Connect\Information\Tools\MichaelVogel.der
set mypath=
set myapp=
set mydev=fr955

Whithin the console you just need to execute 'c ?' to see the help page or for instance 'c frixl' to compile a release version of your app, show some information, delete temporary files and run the app in the simulator...

Batch file c.cmd

C.zip