Development Tools

Wow nice just gave these a quick go and they look great!

The font viewer looks very useful for checking over and verifying fonts. (For anyone else trying this just drag a .fnt file over it when it asks).

I didn't manage to actually compile anything in Screeny itself though - maybe I need some extra environment stuff set up? Or need to copy the project somewhere else?

First off I noticed that "C:" doesn't work after browsing for my developer key - instead I had to set it to "*:" manually. If I didn't do that then it tried to revert to your default key file.

Then when compiling any of the samples I get this error: Provided device id 'round watch' is invalid. I can't copy the text from your compiler output so it's a bit hard to give more information than that sorry. Ah it does say also: warning no make options have been set. Any suggestions?

Edit: a note for the font viewer - I just tried a font with 2 pages and only glyphs from the texture for the 2nd page are visible :-)

Thanks for your nice comments...

Concerning the font viewer - I've never made a multi page font, will check that...
...made a quick update (paged fonts should work now, there's no big comfort, but you can switch pages by pressing 'P' and 'Shift+P')

The Screeny tool is maybe a little bit more tricky - at the beginning it was just made to do nice screenshots for the Garmin IQ app store...
...anyhow some ideas and notes:

• Did you use the "browse" button to set your key file? Where is it located on your PC? What was the result in the Option dialog?
• For newer SDKs (3.x) there's no round watch device anymore. You should add a parameter to your project name representing another device (Project 9 would compile the project for the Forerunner 935)
  Alternatively you could press Strg+F3 to choose from a list (hopefully your device is listed here)
• Other compiling options are a little bit restrictive for now (so doing most things within the manifest is a good idea) - but try a Shift+F1 to see available options (Project r9* would add the resource.xml and makes a release without debugging information)

If you still have problems, please forward the console output to me. You can copy a single line or even the full output window to the clipboard by pressing Ctrl+C (two times for the full list). If you want to see more details in the output window, enable "verbose debugging" which shows the java call commands and some other things...

Nice - the font page switching is cool, thanks

For the key file in Screeny I used browse to find it. It is at: C:\Garmin\dev\developer_key.der. After the browse it had put "C:\Garmin\dev\developer_key.der" in the string. I then had to edit it to "*:\Garmin\dev\developer_key.der" like the other paths for it to work. But I just reopened Screeny and it was straight away showing "C:\Garmin\dev\developer_key.der" and seems ok with that now ... so I'm uncertain what the problem might be.

I will try and get the compiling to work again later when I have some time, so thanks for the tips.

Thanks for your additional information...

If compiling fails, you may press Ctrl+Shift+Z (verbose debugging) and retry compiling (Ctrl+Enter)...

This should bring up a line like the following:

: set path=%path%;"..."&java -cp "C:\...monkeybrains.jar"; com.garmin.monkeybrains.Monkeybrains -a "C:\..." -u "C:\...\devices.xml" -o "Example.prg" -m "...\manifest.xml"  --release --device fr935 -z "C:\...\resources.xml" "C:\...\Example.mc"  -y "...\Key.der" 2>Screeny.out

Hope that will show what is going wrong here...

New versions of Screeny and ScreenyFont are available...

Screeny should be able to support more devices (Ctrl+F3) on the simulator now (keyboard control, etc.)
I have no idea for now, why newer Connect IQ SDKs need to start java with elevated rights, but anyhow it can be done now (Ctrl+Shift+F12)
Many more other improvements, like support of "Notepad++", "Programmers Notepad"...

ScreenyFont can also be used now to add characters to a font file (Ctrl+N) and some mouse control has also been done (Ctrl+M toggles the edit mode)...

I know I should write something like a manual but there are not the best chances for that because I am extremely lazy...

Time for a new version of the Screeny Font Tool

Some of the latest changes:

• 'M' toggles the status messages (enabling them will show you what has been done when pressing a shortcut),
• Ctrl+Z toggles between zooming modes
• Space/F5 improved reloading of a font (when you do parallel editing with a paint program)
• F1 help screen text is placed in the visible area of the window

Have fun!

If anyone is interested to add a simple pixel editor into the Screeny Tool, please do a reply here...

Thank you for the tool.

Up!

Thanks for your positive feedback

Here you can download updated 64Bit-Windows versions for the editor and the screeny tool. The editor includes a pixel editor for quick changes now, the screeny tool allows to switch easily between different SDK sets, like GIQ 2.1and 3.1.

There's still one annoying thing - when using a SDK 3.0 or higher, my program needs to be started with administrator rights. This seems to be related to the compiler and simulator which use different temporary file locations now. Anyhow it would be nice if Garmin would be able to sort this out.

Time for a new update of the font editor: now you can create multiple font sizes more easily. Please play around within the pixel editor (Ctrl+D), the help page below is not complete at the moment, so just play around, quite a lot of things should be intuitive.

As seen below, a lot of functions are available with selections, just try Ctrl+F, R, N, M, I and so on as seen below...

32 bit version

64 bit version