It might be a OS limitation but I ask you, does/can this program give us smooth non-rotational animations? For the backgrounds ? As smooth as any rotational features? This 1 second per frame is killing me.
And, can this allow more then 10 images per array ?
These two items are huge limitations but I think these are limitations set by the watches MTK OS.
But I must ask…
Aug 31, 2017 8:54:02 GMT 1 jacek said:
Marco - do we can change time, date and other things for this preview instead of 10:09:34?
Not yet, but this is a feature I've been thinking about...
Aug 31, 2017 9:56:19 GMT 1 ricktop said:Aug 30, 2017 22:25:17 GMT 1 mpmf said:
WatchFace Designer v.0.6 released
Just played with the template feature :
Thank you for sharing the template. Nice work. Just a tip on an hidden feature: As you know, when the original image does not have the transparent area already defined we must add it. After placing the transparent area, when we are placing the watch face, and with the watch face selected, if you press CTRL+SHIFT and click on the transparent area, the watch face will automatically place itself in the transparent area. This can save a lot of time
By the way, if you have any suggestions to make it easier to make templates, I’d love to hear them.
Aug 31, 2017 10:45:58 GMT 1 deputydaves said:
It might be a OS limitation but I ask you, does/can this program give us smooth non-rotational animations? For the backgrounds ? As smooth as any rotational features? This 1 second per frame is killing me. And, can this allow more then 10 images per array ? These two items are huge limitations but I think these are limitations set by the watches MTK OS. But I must ask…
Yes, both are OS limitations. Or, to be more precise, they are clock engine (on the watch) limitations. There's nothing I can do about it apart creating an entire new launcher, with a different watch face format... The array size is dependent on the type. For instance, the month array is 12 images, while the weather array is 15 images. But none of these are helpful to create animations.
Great job !
I have a question and a suggest
Question : i try to build my first face with your tool, and it is a 24h watch (hour hand makes a turn in 24 hours). I made it, but the hand makes 24 steps. I would like the 24H hand turns slowly, a turn in 24h made slowly.
Suggest : it would be nice to hide a layer in your tool, useful sometimes when we build a watch
Aug 31, 2017 16:23:20 GMT 1 PalmBox said:
Great job !I have a question and a suggest
Question : i try to build my first face with your tool, and it is a 24h watch (hour hand makes a turn in 24 hours). I made it, but the hand makes 24 steps. I would like the 24H hand turns slowly, a turn in 24h made slowly.
Suggest : it would be nice to hide a layer in your tool, useful sometimes when we build a watch
Thanks for the kind words. Regarding your question, if you set the AutoRotation property to HOUR_24, it will rotate smoothly in preview. In the watch, however, I don’t know, because I don’t have one yet. And it seems that I have contradictory results on ClockSkin Maker (where the handle jumps in 24 steps) and in Eric’s Standalone launcher (where the 24 hour handle movement is smooth). If you have set the auto rotation to HOUR_24 and is not smooth in your watch, then there is nothing I can do, because that’s how the clock’s engine works, and I can’t change it…
Regarding your suggestion, it’s something on my to do list. I’m not prioritizing it yet because you can already sort of do it by changing the property “Opacity” to 0. In that case it will not be visible. I know this is a workaround and not a true solution and it’s not very practical, but I haven’t had the time yet. I will do it, hopefully before the 1.0 release. Thanks for the suggestion any way and feel free to suggest more things.
Thanks for answer. I confirm that, on your apps, i can have a smooth movement preview on my 24H first watch (a botta uno24 plus), but on Closksin on the watch, i have only 24 steps, no smooth
Hi again, and thanks for another revision of your great program!
Have not tried it yet, but is the “rescale option for DigitalClock layers” the function I suggested on August 1? If so, I’m very exited to try it out.
Another small thing: Unless I’ve overlooked something - is it possible to remove leading zeros on e.g. day-of-month?
Aug 31, 2017 11:34:42 GMT 1 mpmf said:
There's nothing I can do about it apart creating an entire new launcher, with a different watch face format...
Or join forces with ricktop and enhance Universal Launcher
Sept 1, 2017 13:06:32 GMT 1 arb2040 said:
Hi again, and thanks for another revision of your great program!Have not tried it yet, but is the “rescale option for DigitalClock layers” the function I suggested on August 1? If so, I’m very exited to try it out.
Another small thing: Unless I’ve overlooked something - is it possible to remove leading zeros on e.g. day-of-month?
Yes it is!!! I’m sorry, I attributed the suggestion to vrmagician, but it was really you who suggested it. I think my age is increasing by eating away my memory
I’ll edit the posts with the name change. It is what you suggested, but with a few more options (resize to fill box changing aspect ratio if necessary, resize to fit box but without changing aspect ratio, and center on box cutting image if necessary)…
About removing the leading zeros, that’s a clock engine thing. I can’t do anything about it, otherwise it would not work on android watches.
EDIT: done editing the previous posts to include your name instead of vrmagician’s in the “requested by”. Sorry for the mix up.
Sept 1, 2017 14:50:57 GMT 1 nameless said:
Or join forces with ricktopand enhance Universal Launcher
No need to… Ricktop’s launcher is already capable of practically anything. If using the clockskin format, it is indeed limited by what the engine supports (ricktop wants exact compatibility), but his launcher also supports watchmaker format, which is a lot more customizable
I know! I love that launcher for that support! (and that’s why my first question in this thread was if you plan to support .watch files. I’m bit tired of text edit watch.xml 
and I love to modify those I can find on net)
Sept 1, 2017 17:20:59 GMT 1 mpmf said:Sept 1, 2017 13:06:32 GMT 1 arb2040 said:
Hi again, and thanks for another revision of your great program!Have not tried it yet, but is the “rescale option for DigitalClock layers” the function I suggested on August 1? If so, I’m very exited to try it out.
Another small thing: Unless I’ve overlooked something - is it possible to remove leading zeros on e.g. day-of-month?
Yes it is!!! I’m sorry, I attributed the suggestion to vrmagician, but it was really you who suggested it. I think my age is increasing by eating away my memoryI’ll edit the posts with the name change. It is what you suggested, but with a few more options (resize to fill box changing aspect ratio if necessary, resize to fit box but without changing aspect ratio, and center on box cutting image if necessary)…
About removing the leading zeros, that’s a clock engine thing. I can’t do anything about it, otherwise it would not work on android watches.
EDIT: done editing the previous posts to include your name instead of vrmagician’s in the “requested by”. Sorry for the mix up.
No problem with the credit for suggestions
I’m just happy that those things were included.
Sept 1, 2017 17:31:50 GMT 1 nameless said:
I know! I love that launcher for that support! (and that's why my first question in this thread was if you plan to support .watch files. I'm bit tired of text edit watch.xml 😁 and I love to modify those I can find on net)
The scripting part of the .watch files is still a problem to me. I can't think on a way to make editing of .watch files simple without loosing or severely limiting the scripting functionality. Or, at least, simpler then watchmaker already does.
On the other hand, I do wish Watchmaker (the editor, not the clock engine) was a desktop app, instead of an android only app. It’s quite hard (for me, at least) to do changes on .watches on the small (5") and limited (no mouse/keyboard) android phone…
Sept 1, 2017 19:11:18 GMT 1 mpmf said:Sept 1, 2017 17:31:50 GMT 1 nameless said:
I know! I love that launcher for that support! (and that's why my first question in this thread was if you plan to support .watch files. I'm bit tired of text edit watch.xml 😁 and I love to modify those I can find on net)
The scripting part of the .watch files is still a problem to me. I can't think on a way to make editing of .watch files simple without loosing or severely limiting the scripting functionality. Or, at least, simpler then watchmaker already does.On the other hand, I do wish Watchmaker (the editor, not the clock engine) was a desktop app, instead of an android only app. It’s quite hard (for me, at least) to do changes on .watches on the small (5") and limited (no mouse/keyboard) android phone…
You can install watchmaker on your PC with Nox emulator… 
mpmf I know… Tried it on tablet and it wasn’t really better. There was a desktop version but it was abandoned.
Scripting I can do just fine in vim but positioning somewhat blindly is a pain. And there is scaling factor as .watch seems to use 512x512 and Eric’s launcher scales it to 400x400 (on my watch at least).
Watch…xml format doesn’t seem complicated but I’m sysadm no coder I make living try to keep running what you guys produce 
Sept 1, 2017 19:55:10 GMT 1 ricktop said:
You can install watchmaker on your PC with Nox emulator... 😀
Good thinking . But I haven’t yet tried the Nox emulator. I usually just use the SDK one (and latest versions support play store, yuppy)
Edit: Just checked, it doesn’t run on Linux… And Android development is a lot faster on Linux then on Windows
Sept 1, 2017 19:58:35 GMT 1 nameless said:mpmf I know... Tried it on tablet and it wasn't really better. There was a desktop version but it was abandoned. Scripting I can do just fine in vim but positioning somewhat blindly is a pain. And there is scaling factor as .watch seems to use 512x512 and Eric's launcher scales it to 400x400 (on my watch at least). Watch..xml format doesn't seem complicated but I'm sysadm no coder I make living try to keep running what you guys produce 😉
Scaling shouldn't be a problem. I use ClockSkins (400x400) on my LG Watch R (360x360), and it doesn't affect anything (asides for image quality, of course). Since Eric's launcher uses OpenGL as the rendering engine, the scaling should be smooth and imperceptible. I also use WatchMaker on my Watch R, and again, it automatically scales to 360x360 from the 512x512 standard resolution, and I don't notice a thing...
Yes, the xml is not complicated, but some of the operations it contains are quite hard to emulate, especially when not using OpenGL (I’m not using it on WFD, but am using it on my wear clockskin engine).
Scaling is problem when you manually insert xy coordinates. Not big one but at times it bites.
I’ve never had any issues with quality of what’s shown on screen 
First, thank for this great tool.
Makes life a lot easier
I have one question / problem.
I’m working on a face with a 24 hour in stead of a 12 hour scale.
I used the HOUR_24 tag and the preview looks ok, but when i install the face the hand dus not show at all.
Is this a known bug or am i doing something wrong.
All other hands seem to work just right
Bert